Date: Thu, 1 May 2003 17:54:10 -0700 From: Joshua Oreman <oremanj@webserver.get-linux.org> To: james_mapson@museum.rain.com Cc: questions@freebsd.org Subject: Re: Remote upgrade Message-ID: <20030502005410.GD63276@webserver.get-linux.org> In-Reply-To: <20030501174011.A96504@ns.museum.rain.com> References: <3EB13FE5.5372.1B4CC40@localhost> <20030501174011.A96504@ns.museum.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 01, 2003 at 05:40:11PM -0700 or thereabouts, James Long seemed to write: > On Thu, May 01, 2003 at 03:40:21PM -0500, boxend@swbell.net wrote: > > When doing a remote upgrade, what is the best way to force the process into the > > background, in case the dialup line for ssh session dies before buildworld finishes. > > > Ensure that /tmp/ has free space to hold a few Megabytes of output, and use: > > # make buildworld >/tmp/make_bw.out 2>&1 & > > Then you can monitor the progress of the make by examining /tmp/make_bw.out > > # tail -f /tmp/make_bw.out > > Control-C will terminate tail, and return you to a shell prompt, > while the make continues to run in the background. > > This is not as sophisticated as using screen, but simpler, and does > not require installing any additional software. But some shells will kill background processes when they log out. Either: * Put `nohup ' in front of the `make' line * Run `disown' right after putting it in the background Note: csh and tcsh users don't need to worry about this. HTH, -- Josh > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030502005410.GD63276>