Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 08 Jul 2020 12:14:02 -0700
From:      Chris <portmaster@BSDforge.com>
To:        bob prohaska <fbsd@www.zefox.net>
Cc:        <freebsd-ports@freebsd.org>
Subject:   Re: Gracefully killing and restarting a port build....
Message-ID:  <65eb133aaf1b8c0ea7002496985e5f44@udns.ultimatedns.net>
In-Reply-To: <20200708034703.GA50491@www.zefox.net>

next in thread | previous in thread | raw e-mail | index | archive | help
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 <PID> aimed at the original make doesn't seem to do anything=2E Even=
=20
> kill -9 <PID> 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 <PID> 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"





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