From owner-freebsd-ports@freebsd.org Wed Jul 8 20:16:25 2020 Return-Path: Delivered-To: freebsd-ports@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 57C8C36E0D8 for ; Wed, 8 Jul 2020 20:16:25 +0000 (UTC) (envelope-from portmaster@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ultimatedns.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4B29Yj0thqz3cgZ for ; Wed, 8 Jul 2020 20:16:24 +0000 (UTC) (envelope-from portmaster@BSDforge.com) Received: from udns.ultimatedns.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by udns.ultimatedns.net (8.15.2/8.15.2) with ESMTPS id 068KGaP1059973 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 8 Jul 2020 13:16:42 -0700 (PDT) (envelope-from portmaster@BSDforge.com) X-Mailer: Cypht MIME-Version: 1.0 Cc: , Ronald Klop In-Reply-To: <20200708153013.GA52503@www.zefox.net> From: Chris Reply-To: portmaster@BSDforge.com To: bob prohaska Subject: Re: Gracefully killing and restarting a port build.... Date: Wed, 08 Jul 2020 13:16:42 -0700 Message-Id: <787354ab5caad4703bd496b5d1188453@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4B29Yj0thqz3cgZ X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; local_wl_ip(0.00)[24.113.41.81] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jul 2020 20:16:25 -0000 On Wed, 8 Jul 2020 08:30:13 -0700 bob prohaska fbsd@www=2Ezefox=2Enet said > On Wed, Jul 08, 2020 at 10:44:03AM +0200, Ronald Klop wrote: > >=20 > >=20 > > Kill the leaf nodes of the process tree=2E So kill the c++ processes=2E Or = type > > ctrl-c if you have control of the terminal=2E >=20 > In this case I'd lost control of the controlling terminal and didn't=20 > know how to recover it=2E After kill -9 of the initial make process= =20 > I left the system standing overnight, to see if killing the original make= =20 > process would eventually propagate down to the leaf nodes=2E It didn't=2E=20 >=20 > Then I used killall c++, and again, it killed the named processes, but ot= her > things, > notably pkg, kept running=2E After waiting a few minutes they were killall-= ed=2E > A notation from ninja eventually showed up in the logfile saying > "interrupted > by user", so maybe ninja was the place to start shutting things down=2E >=20 > > If you are running the compile in a jail (like poudriere) you might use > > "killall -j c++" or something similar=2E >=20 > No room for a jail on a Pi, alas=2E=2E=2E=2E > > Pkill can be usable also=2E > Thank you, I didn't know about it=2E > > BTW: How graceful a restart works is outside of the scope of the ports > > framework and depends a lot on the structure of the chromium build proc= ess > > itself=2E > > > Understood=2E This is the first time I've ever needed to kill a port build=2E > Usually they die prematurely of natural causes! FWIW should you need to attempt such a strategy again=2E You'll want to add sh (/bin/sh) to the list of potential "victims" in your kill list=2E :-) --Chris >=20 > Thanks for your help >=20 > bob prohaska >=20 > _______________________________________________ > freebsd-ports@freebsd=2Eorg mailing list > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd=2Eorg"