Really quick Unix question....

[gopunk]

what's the command to run a job not connected to your terminal? i.e., after you log off it still runs...

i know there is screen, but there is something else too...

 

[KK]

cron ???

KK

 

[blackdogdeek]

i think there are also "at" jobs aren't there? to be run at a designated time no?

 

[Entity]

Cron to run jobs at a later time/date.

Screen for starting a job, detatching it, then logging out.

Rob

 

[gopunk]

thanks guys... i mean one that will start the job immediately... i heard another guy mention it at school, it wasn't cron or at...

 

[Bootprint]

You can put it in the background by adding &

 

[Beattie]

& ?

that forces the process into the background so that you can still work on the terminal... like

# mozilla &

Also, you can use CTRL-Z then bg to make a foreground process run in the background. and then fg to bring it forward.

 

[dabuddha]

Originally posted by: Bootprint
You can put it in the background by adding &

 

[marleymarl]

^^ what he said

 

[Entity]

Yeah, you can bg a process by adding &.

 

[Nitemare]

end it with an & or nohup it

 

[gopunk]

NOHUP

i think that's what i was looking for... thanks! oh yea and the & stuff works too... i dunno why i thought it wouldn't... probably because whenever i use it with emacs and i close the terminal, emacs dies

 

[atom]

Eh, you sure & works? & only put things into the background, when you log off your terminal it will kill all your processes.

 

[gopunk]

Originally posted by: atom
Eh, you sure & works? & only put things into the background, when you log off your terminal it will kill all your processes.

yea for some weird reason it does... that's what i thought too

i dunno how to get it back though... i can see in top but i dunno how to resume it (bg doesn't show it)...

how do you get it back if you use nohup? or do you just have to look at nohup.out and kill the process if you don't want it anymore...

 

[Pepsi90919]

so make it run under somebody else then.

 

[Bootprint]

If the job is in the background use jobs and fg.

 

[gopunk]

Originally posted by: Bootprint
If the job is in the background use jobs and fg.

fg doesn't show anything and jobs doesn't either... but the process shows up in top. hmmmmm

 

[Pepsi90919]

i thought you said it wasn't running?

 

[gopunk]

Originally posted by: Pepsi90919
i thought you said it wasn't running?

no it is running, i just have no idea how to get back to it... bring it to the foreground

 

[ys]

Originally posted by: gopunk
NOHUP

i think that's what i was looking for... thanks! oh yea and the & stuff works too... i dunno why i thought it wouldn't... probably because whenever i use it with emacs and i close the terminal, emacs dies

You can do disown emacs from the terminal.
$emacs &
$disown emacs
or just do "emacs & disown"

I don't know if that answers your original question though...

 

[atom]

You can also run the process in a subshell and I don't think it will kill it when you log out of your current session. Also, you can configure your shell to not kill background processes when you log out, although I don't think this is that great of an idea personally.

As far bringing back a process to foreground after using nohup, I have no clue.

 

[silverpig]

I always just use &

./setiathome &

 

[Nitemare]

Originally posted by: gopunk

Originally posted by: atom
Eh, you sure & works? & only put things into the background, when you log off your terminal it will kill all your processes.

yea for some weird reason it does... that's what i thought too

i dunno how to get it back though... i can see in top but i dunno how to resume it (bg doesn't show it)...

how do you get it back if you use nohup? or do you just have to look at nohup.out and kill the process if you don't want it anymore...

ps "project name"

kill -9 "process number"

 

[Dracos]

Ahhh kill -9

The end all be all for most of your unix problems.