Sorry for such lame question but .. When i am connected to server using SSH . How can i fetch process to background and close ssh session and not kill that process? And how can i later connect to server and fetch process from background to console? All years i have been using "screen" for this. Thanks in advance! David -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20080715/f6d8f685/attachment-0002.html>
On Tue, 2008-07-15 at 14:34 +0200, David Hl??ik wrote:> Sorry for such lame question but .. > > When i am connected to server using SSH . How can i fetch process to > background and close ssh session and not kill that process? And how > can i later connect to server and fetch process from background to > console? > > All years i have been using "screen" for this.IIUC your question, the bash job control facility should allow what you need. "Man bas:, see JOB CONTROL.> > Thanks in advance! > > David > <snip sig stuff>HTH -- Bill
David Hl?c(ik wrote:> Sorry for such lame question but .. > > When i am connected to server using SSH . How can i fetch process to > background and close ssh session and not kill that process? And how can i > later connect to server and fetch process from background to console? > > All years i have been using "screen" for this.Why not continue with screen on CentOS? yum install screen Mogens -- Mogens Kjaer, Carlsberg A/S, Computer Department Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark Phone: +45 33 27 53 25, Fax: +45 33 27 47 08 Email: mk at crc.dk Homepage: http://www.crc.dk
On Tue, Jul 15, 2008 at 08:34, David Hl??ik <david at hlacik.eu> wrote:> When i am connected to server using SSH . How can i fetch process to > background and close ssh session and not kill that process? And how can i > later connect to server and fetch process from background to console?Ctrl-Z will suspend the process, then run the "bg" command to continue running it on background, then run "disown %1" to make your shell "forget" about the job and not send it a HUP (Hang-Up) signal when you log out from it. I works, unless your process will try to read from stdin, in that case it might be killed because there is no controlling tty (or something to that effect). In general, though, running it on a "screen" session is a much better alternative, because you then can detach (Ctrl-A, d) and reattach (screen -xRR) to continue watching the output. The only problem is that you must remember to use "screen" *before* you start running your process... HTH, Filipe