Fork a child process off to initiate the ssh/rsh remote process and let the parent go on about its business. Note: make certain that the child has enough intelligence built in to act appropriately when confronted with an error. I am very fond of sending an email reguardless of the outcome. I always get confirmation that the child process completed.
----
I Go Back to Sleep, Now.
OGB
| [reply] |
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. | [reply] |
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] |
| [reply] |
I mayn not be understanding you, but could you ust put the process into the background? Then you won't be waiting on output.
> ./run_this_script &
qq | [reply]
[d/l] |