On 2020-07-08 14:53, bob prohaska wrote:
>
> AIUI, screen runs until the session terminates and then stops...
I'm a tmux user now, but I never experienced this behavior when I used
screen. Screen was my go-to workaround for a flaky Internet connection
to the host I was trying to manage. Tmux cert
On Wed., Jul. 8, 2020, 2:53 p.m. bob prohaska, wrote:
> 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 complet
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, sc
On Wed, 8 Jul 2020 08:30:13 -0700 bob prohaska f...@www.zefox.net said
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
On Tue, 7 Jul 2020 20:47:03 -0700 bob prohaska f...@www.zefox.net 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).
On the plus side, it hasn't crashed, despite several days of
continuous swapping with 1-2GB of
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.
On 7/8/20 9:30 AM, bob prohaska wrote:
> On Wed, Jul 08, 2020 at 10:44:03AM +0200,
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
Van: bob prohaska
Datum: woensdag, 8 juli 2020 05:47
Aan: freebsd-ports@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
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
