Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 08 Jul 2020 13:16:42 -0700
From:      Chris <portmaster@BSDforge.com>
To:        bob prohaska <fbsd@www.zefox.net>
Cc:        <freebsd-ports@freebsd.org>, Ronald Klop <ronald-lists@klop.ws>
Subject:   Re: Gracefully killing and restarting a port build....
Message-ID:  <787354ab5caad4703bd496b5d1188453@udns.ultimatedns.net>
In-Reply-To: <20200708153013.GA52503@www.zefox.net>

next in thread | previous in thread | raw e-mail | index | archive | help
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 <pid> 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 <jail> 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"





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?787354ab5caad4703bd496b5d1188453>