On Sun, Nov 18, 2018, 11:04 Damien Miller ok djm
>
> why does mosh depend on the stderr of a proxycommand?
>
Based on my extensive (ie 5 minute) study of the code, it's turtles all the
way down. mosh invokes ssh with a proxycommand that invokes mosh again in
a different mode, my guess is so
On Sun, 18 Nov 2018 10:10:30 +1100, Darren Tucker
wrote:
> On Sun, Nov 18, 2018 at 10:03:20AM +1100, Darren Tucker wrote:
> You can work around it by setting ControlPersist=yes either in
> ~/.ssh/config or via mosh's --ssh option.
> ok?
This diff makes mosh work again, thanks!
(ok danj@
On Sun, Nov 18, 2018 at 10:03:20AM +1100, Darren Tucker wrote:
> On Sun, 18 Nov 2018 at 09:48, Darren Tucker wrote:
>
> > Was able to reproduce and confirmed by bisecting that the "redirect stderr
> > of ProxyCommands to /dev/null when ssh is started with ControlPersist"
> > change is where it
On Sun, 18 Nov 2018 at 09:48, Darren Tucker wrote:
> Was able to reproduce and confirmed by bisecting that the "redirect stderr
> of ProxyCommands to /dev/null when ssh is started with ControlPersist"
> change is where it breaks, but I don't understand what mosh is doing under
> the covers that
Was able to reproduce and confirmed by bisecting that the "redirect stderr
of ProxyCommands to /dev/null when ssh is started with ControlPersist"
change is where it breaks, but I don't understand what mosh is doing under
the covers that now doesn't work. Will look further.
--
Darren Tucker
On Sat, 17 Nov 2018, Adam Stouffer wrote:
> On 11/17/2018 10:58 AM, Peter Hessler wrote:
> >
> > Yes, the fix is "don't use a single root partition" and instead
> > "partition your damn disk as intended".
>
> So what is the maximum root partition size or don't you know because
> this is an
On 11/17/2018 10:58 AM, Peter Hessler wrote:
Yes, the fix is "don't use a single root partition" and instead
"partition your damn disk as intended".
So what is the maximum root partition size or don't you know because
this is an unintended bug?
I've been an OpenBSD user for nearly 20
On Sat, Nov 17, 2018 at 09:47:19PM +1100, Darren Tucker wrote:
> On Sat, 17 Nov 2018 at 18:29, Matthieu Herrb wrote:
>
> > on amd64-current on the client side, mosh now fails to connect to
> > remote hosts :
> >
> > /usr/local/bin/mosh: Did not find remote IP address (is SSH ProxyCommand
> >
On 2018 Nov 17 (Sat) at 00:57:54 -0700 (-0700), astouffer wrote:
:Just running into this same exact problem on my box and it started with 6.4.
:It's been running releases for years now but 6.4 is stuck in a boot loop
:with the heap full error. The box is a Core2 E6750 with 2Gb of memory and
:one
Just running into this same exact problem on my box and it started with 6.4.
It's been running releases for years now but 6.4 is stuck in a boot loop
with the heap full error. The box is a Core2 E6750 with 2Gb of memory and
one single root partition on a 160Gb drive. Any fixes for this problem in
Please don't use bugs@ for feature requests. The safest bet for getting
a feature in the future is to send a diff.
... this said, I think your particular problem can be solved by using
bioctl(8) to build a softraid with CONCAT discipline to combine physical
disk partitions into a "logical
On Sat, 17 Nov 2018 at 18:29, Matthieu Herrb wrote:
> on amd64-current on the client side, mosh now fails to connect to
> remote hosts :
>
> /usr/local/bin/mosh: Did not find remote IP address (is SSH ProxyCommand
> disabled?).
> Exit 10
>
What does the client's ~/.ssh/config look like for that
12 matches
Mail list logo
