I've been having problems getting my new installation of SuSE 9.2 pro to have a stable connection to the internet (which I'm troubleshooting separately). While dealing with this problem, I have noticed that anytime I log in from a remote location and start a batch job running in the background (using the statistical analysis software SAS), the job gets killed as soon as my SSH session is terminated. This is making it really hard to get any work done!

Does anyone have any idea how I might start troubleshooting to get my remotely started batch programs to continue running even if my internet connection flakes out?

Many thanks.

take a look at this thread:

http://www.linuxquestions.org/questi...hreadid=261399

Thanks! The nohup command definitely fixes the problem!

When I used to run SAS jobs on a unix machine, the default was that when a session was killed, the jobs started from that session continued running, so this problem caught me off-guard.

I'm very happy for the easy work-around. Thanks again redgren.