in reply to Run a remote script

Check out nohup (section 1 of the man pages). On some systems (I believe Solaris for eg) when you close your ssh connection all of the open jobs you have open are sent a HUP signal. Chances are your program is being killed by this signal (many are). Using nohup will cause the HUP to be ignored so your process won't die when you log out. You just run your command as " nohup my_background_job & " instead of as " my_background_job & ". Let us know if that helps solve it.

Replies are listed 'Best First'.
Re^2: Run a remote script
by MidLifeXis (Monsignor) on Jul 14, 2004 at 16:52 UTC

    If the jobs are left running or killed is a function of the shell. For example (IIRC), csh, by default, will let them run. On the other hand, ksh, will not. You can change that behavior by nohupping under some shells, disconnecting from the process group and terminal, stty tostop, etc.

    --MidLifeXis

[reply]

In Section Seekers of Perl Wisdom