Gracefully killing and restarting a port build....

[Ronald Klop]

Van: bob prohaska <fbsd at www.zefox.net>
Datum: woensdag, 8 juli 2020 05:47
Aan: freebsd-ports at freebsd.org
Onderwerp: Gracefully killing and restarting a port build....
> 
> 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).
> 
> On the plus side, it hasn't crashed, despite several days of
> continuous swapping  with 1-2GB of swap in use. Kudos to the
> VM folks.
> 
> Now I'd like to (gracefully) stop the make and restart it with more
> sane -j values. -2 seems like a reasonable start.
> 
> A simple
> kill <PID> aimed at the original make doesn't seem to do anything. Even
> kill -9 <PID> appears to have no effect on the c++ threads, which are
> still running minutes afterwards.
> 
> Now it seems rather like I'm stuck: The original <PID> is gone, but
> c++ is still grinding away as if nothing has changed..
> 
> Is there a better way to accomplish a clean(ish) stop and restart of
> a multi-threaded make process?
> 
> Thanks for reading, apologies if it's a dumb question,
> 
> bob prohaska
>  
> 
> 
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
> 
> 
> 


Kill the leaf nodes of the process tree. So kill the c++ processes. Or type ctrl-c if you have control of the terminal.
If you are running the compile in a jail (like poudriere) you might use "killall -j <jail> c++" or something similar.
Pkill can be usable also.
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 process itself.

Regards,
Ronald.