Background Job "Stopped" with SSH

最新推荐文章于 2024-09-27 14:17:56 发布

原创最新推荐文章于 2024-09-27 14:17:56 发布 · 1.2k 阅读

0 ·

CC 4.0 BY-SA版权

本文介绍了一种常见问题的解决方案：当通过SSH远程执行后台任务时，由于SSH会话挂起导致任务中断。文章提供了具体的解决办法，即通过重定向三个I/O流来避免这一问题。

运行了一个后台程序，此程序调用SSH远程执行另外的任务，当多个这样的后台程序执行的时候，状态经常从Running 变为Stopped，导致程序中断。

解决办法，覆盖三个I/O，具体参考：http://en.wikipedia.org/wiki/Nohup

Overcoming hanging

Note - Nohupping backgroundedjobs is typically used to avoid terminating them when logging off from aremote SSH session. A different issue that oftenarises in this situation is that ssh is refusing to log off("hangs"), since it refuses to lose any data from/to the backgroundjob(s).^[6][7] Thisproblem can also be overcome by redirecting all three I/O streams:

nohup./myprogram > foo.out 2> foo.err < /dev/null &

Also note that a closingSSH session does not always send a HUP signal to depending processes. Amongothers, this depends on whether a pseudo-terminalwasallocated or not.^[8]