On Wed, Jul 08, 2020 at 09:34:53AM -0600, Janky Jay, III wrote: > In the future, if you can, try using "screen" or "tmux" to run these > large builds in so you don't take the risk of losing the > terminal/console. Or, maybe I'm completely off-base as to how it was > lost to begin with. >
AIUI, screen runs until the session terminates and then stops. In my case the controlling terminal was lost when the ssh connection broke. Thus, I think screen would have quit as well. Just why ssh connections keep breaking is a mystery of long standing. I've been blaming it on feeble wifi between my workstation (a Pi3B+) and WAP (D-Link DI524) but have no persuasive evidence. Not usually a big deal. The build was started using something like make [options] > make.log & so it kept beavering away after ssh gave up and still existed when I looked for it with ps -a. There were still other ssh connections open and running at the same time. Is there some way to re-attach a running background job to a new controlling terminal? Thanks for writing! bob prohaska > On 7/8/20 9:30 AM, bob prohaska wrote: > > On Wed, Jul 08, 2020 at 10:44:03AM +0200, Ronald Klop wrote: > >> > >> Kill the leaf nodes of the process tree. So kill the c++ processes. Or > >> type ctrl-c if you have control of the terminal. > > In this case I'd lost control of the controlling terminal and didn't > > know how to recover it. After kill -9 <pid> of the initial make process > > I left the system standing overnight, to see if killing the original make > > process would eventually propagate down to the leaf nodes. It didn't. > > > > Then I used killall c++, and again, it killed the named processes, but > > other things, > > notably pkg, kept running. After waiting a few minutes they were killall-ed. > > 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. > > > >> If you are running the compile in a jail (like poudriere) you might use > >> "killall -j <jail> c++" or something similar. > > No room for a jail on a Pi, alas.... > >> Pkill can be usable also. > > Thank you, I didn't know about it. > >> 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. > >> > > Understood. This is the first time I've ever needed to kill a port build. > > Usually they die prematurely of natural causes! > > > > Thanks for your help > > > > bob prohaska > > > > _______________________________________________ > > freebsd-ports@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" _______________________________________________ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
