From nobody Wed Jun 9 00:36:51 2021 X-Original-To: freebsd-ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 5D9FAF7B63F for ; Wed, 9 Jun 2021 00:36:58 +0000 (UTC) (envelope-from kpn@neutralgood.org) Received: from gunsight1.neutralgood.org (gunsight1.neutralgood.org [IPv6:2607:f758:2280:1:d6be:d9ff:feac:a1e9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "gunsight1.neutralgood.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4G07Tk1kzLz3nWW for ; Wed, 9 Jun 2021 00:36:57 +0000 (UTC) (envelope-from kpn@neutralgood.org) Received: from gunsight1.neutralgood.org (localhost [127.0.0.1]) by gunsight1.neutralgood.org (8.16.1/8.15.2) with ESMTPS id 1590aps2022031 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 8 Jun 2021 20:36:51 -0400 (EDT) (envelope-from kpn@gunsight1.neutralgood.org) Received: (from kpn@localhost) by gunsight1.neutralgood.org (8.16.1/8.15.2/Submit) id 1590apod022028; Tue, 8 Jun 2021 20:36:51 -0400 (EDT) (envelope-from kpn) Date: Tue, 8 Jun 2021 20:36:51 -0400 From: "Kevin P. Neal" To: bob prohaska Cc: FreeBSD Ports Subject: Re: Stopping and restarting poudriere Message-ID: References: <20210608145624.GA22166@www.zefox.net> <20210608232954.GA26003@www.zefox.net> List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210608232954.GA26003@www.zefox.net> X-No-archive: Yes X-Rspamd-Queue-Id: 4G07Tk1kzLz3nWW X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Tue, Jun 08, 2021 at 04:29:54PM -0700, bob prohaska wrote: > Three actions seem possible: Change the ssh session (move to another > workstation), reboot the workstation or reboot the poudriere builder. > Using screen for the connection instead of ssh would likely allow > the first two, but I didn't plan that far ahead. > > My question was inspired by a hazy memory of something called > "checkpointing" a job on a mainframe. I think it was in the mid > 1980's. I believe it involved something like a core dump which > was then reloaded from disk and restarted later on. > > Surely anthing possible then should be trivial now 8-) > > I tried using control-C in two cases. In the first, which was > intentional, poudriere didn't want to restart, saying the jail > was still running. I had to kill the jail explictly, suggesting > the kill wasn't complete. In the second case the kill was accidental > but the restart was uneventful. Together, it suggests control-C isn't > a good way to stop poudriere. > > For now, it seems the answer is "Let poudriere finish!". I have issues with my ISP where my ssh sessions die at random times, usually (but not always) when I'm away from the computer. So solution for Poudriere was to run it in the background and pipe stdout+stderr to a file in /tmp. Then a tail -f on that file and it's almost as good as running it in the foreground -- but with the advantage that if the connection goes I can just log back in and tail -f again. I also have a script that runs in another window with the output of "poudriere status -b" followed by "sleep 4" in a loop. That way I can just glance to that side of my monitor to see how things are going. -- Kevin P. Neal http://www.pobox.com/~kpn/ "Good grief, I've just noticed I've typed in a rant. Sorry chaps!" Keir Finlow Bates, circa 1998