Jobs started with nohup aborts after closing ssh

awalls · 09-25-2007, 01:04 PM

I have a user who runs jobs in Flow3d on RedHat Linux enterprise ws4 X86_64. His command line structure is nohup command & . So he is running both nohub and putting it in the background. Standard output and standard error are nohup.out. When he logs out of ssh his job aborts. If any one knows why this is or what can be done about it it would be much appreciated.

Hangdog42 · 09-25-2007, 03:11 PM

Have your user use the screen command to create virtual terminals. Those survive logging out and can be picked back up by next time they log in.

matthewg42 · 09-25-2007, 04:31 PM

Screen is very good for this sort of thing. Plus you can re-connect to a screen session at a later time, even if you log out, and log back in on a different tty. e.g. You wake up, log into work from home using ssh, and start some program in a screen session. You disconnect the screen session from the tty, and drive to work. Then you log into the machine locally, and use "screen -r" to re-connect to the program, at which point you can interact with it again.

Screen rules.

awalls · 09-28-2007, 05:20 AM

Yeah I'm using screen as an alternative. I would still like to know why nohup is not working. It used to work fine in earlier distribution's.

matthewg42 · 09-28-2007, 05:26 AM

Yes, it's curious, I would have thought it would work.