From owner-freebsd-ports@freebsd.org Wed Jul 8 19:13:53 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 A720936C370 for ; Wed, 8 Jul 2020 19:13:53 +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 4B289V6m7Hz3Tcc for ; Wed, 8 Jul 2020 19:13:50 +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 068JDuSZ058160 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 8 Jul 2020 12:14:05 -0700 (PDT) (envelope-from portmaster@BSDforge.com) X-Mailer: Cypht MIME-Version: 1.0 Cc: In-Reply-To: <20200708034703.GA50491@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 12:14:02 -0700 Message-Id: <65eb133aaf1b8c0ea7002496985e5f44@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4B289V6m7Hz3Tcc 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 19:13:54 -0000 On Tue, 7 Jul 2020 20:47:03 -0700 bob prohaska fbsd@www=2Ezefox=2Enet said > While compiling www/chromium on a Pi3B it has become clear that the > default -j4 isn't going to work (yes, I know, ya told me)=2E=20 >=20 > On the plus side, it hasn't crashed, despite several days of > continuous swapping with 1-2GB of swap in use=2E Kudos to the > VM folks=2E >=20 > Now I'd like to (gracefully) stop the make and restart it with more=20 > sane -j values=2E -2 seems like a reasonable start=2E=20 >=20 > A simple=20 > kill aimed at the original make doesn't seem to do anything=2E Even= =20 > kill -9 appears to have no effect on the c++ threads, which are > still running minutes afterwards=2E=20 >=20 > Now it seems rather like I'm stuck: The original is gone, but=20 > c++ is still grinding away as if nothing has changed=2E=2E=20 >=20 > Is there a better way to accomplish a clean(ish) stop and restart of > a multi-threaded make process? >=20 > Thanks for reading, apologies if it's a dumb question, Not at all=2E :-) I usually leverage multiple terminals, and simply dedicate one to the/a build session=2E So simply issuing a ^C to that terminal sends an INTR to the parent, and children=2E I've experienced no problems restarting the process (build) after doing so=2E HTH! :-) --Chris >=20 > bob prohaska >=20 >=20 >=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"