Date: Tue, 7 Aug 2007 12:18:01 -0500 From: Eric Crist <mnslinky@gmail.com> To: Rakhesh Sasidharan <rakhesh@rakhesh.com> Cc: Narek Gharibyan <ngharibyan@mail.ru>, freebsd-questions@freebsd.org, 'Xihong Yin' <xyin@bluebottle.com> Subject: Re: restart network without shutdown Message-ID: <006F1C69-C0CC-4837-B22D-CBA39B1067D8@gmail.com> In-Reply-To: <20070807210914.P84583@obelix.home.rakhesh.com> References: <Pine.CYG.4.58.0708070859220.3944@OHD12-8386.nws.noaa> <001201c7d906$58e8ee40$180ca8c0@arm.synisys.com> <1F65B63B-94D0-4AD5-A128-D5C03875E052@gmail.com> <20070807210914.P84583@obelix.home.rakhesh.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 7, 2007, at 12:11 PMAug 7, 2007, Rakhesh Sasidharan wrote: > > Eric Crist wrote: > >> Install screen from ports, run it from within screen. >> >> You'll still get disconnected, but you should be able to reconnect >> after it's done. Screen will allow the script to complete, >> whereas your ssh session is killing it half/part way through... >> >> HTH >> > > Just curious -- how come screen works in such situations? I > recollect someone else too recommending screen a few days ago > (instead of "watch" to connect to another terminal) coz it doesn't > get cut. The SSH session in which screen runs gets disconnected, > but screen still works ... useful! > Screen can detach and run in the background. Processes which start from within screen don't get killed, because, screen, the parent process, is still running. The reason the script dies when you get d/ c'd is that your shell, the parent process, has died. HTH Eric Crist
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?006F1C69-C0CC-4837-B22D-CBA39B1067D8>