Date: Wed, 8 Jul 2020 15:50:19 -0700 From: Freddie Cash <fjwcash@gmail.com> To: bob prohaska <fbsd@www.zefox.net> Cc: "Janky Jay, III" <jankyj@unfs.us>, freebsd-ports <freebsd-ports@freebsd.org> Subject: Re: Gracefully killing and restarting a port build.... Message-ID: <CAOjFWZ5phK3T=5-2KOn9%2BuaWD18ujJR_PCmsRHYhJgaUy=fAXA@mail.gmail.com> In-Reply-To: <20200708215341.GB52503@www.zefox.net> References: <20200708034703.GA50491@www.zefox.net> <941930819.28.1594197843269@localhost> <20200708153013.GA52503@www.zefox.net> <25c3b51c-6fa2-4d69-cb39-5ac7802fc658@unfs.us> <20200708215341.GB52503@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed., Jul. 8, 2020, 2:53 p.m. bob prohaska, <fbsd@www.zefox.net> wrote: > On Wed, Jul 08, 2020 at 09:34:53AM -0600, Janky Jay, III wrote: > > In the future, if you can, try using "screen" or "tmux" to run these > > large builds in so you don't take the risk of losing the > > terminal/console. Or, maybe I'm completely off-base as to how it was > > lost to begin with. > > > > AIUI, screen runs until the session terminates and then stops. In my case > the controlling terminal was lost when the ssh connection broke. Thus, I > think screen would have quit as well. Nope. Screen (or tmux which is nicer to use, imo) takes over as the controlling terminal. When the ssh connection terminates, screen continues running (along with all the processes started in that screen session). You reconnect via ssh, and connect to the running screen session and carry on like nothing happened. Cheers, Freddie Typos due to smartphone keyboard.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOjFWZ5phK3T=5-2KOn9%2BuaWD18ujJR_PCmsRHYhJgaUy=fAXA>