The problem is just fixed on the tree. Thanks.
The problem was come from my "TCP receive buffer size auto scaling"
commit. https://marc.info/?l=openbsd-cvs=166781979228293=2
On Thu, 1 Dec 2022 13:05:25 +0100
Christian Weisgerber wrote:
> Jeremie Courreges-Anglas:
>
>> > The pattern is that
Jeremie Courreges-Anglas:
> > The pattern is that several ssh processes are spawned in parallel
> > that connect to different hosts--actually the amd64*.p package build
> > machines. I have observed this both from home a continent away,
> > and from amd64.p to amd64-*.p on the same network.
>
>
On Wed, Nov 30 2022, Christian Weisgerber wrote:
> For at least two weeks, I have observed a strange error on OpenBSD/amd64
> -current, across multiple snapshots and rebuilds from source during
> that time:
>
> When several ssh processes are spawned in quick succession, SOMETIMES
> one of them
For at least two weeks, I have observed a strange error on OpenBSD/amd64
-current, across multiple snapshots and rebuilds from source during
that time:
When several ssh processes are spawned in quick succession, SOMETIMES
one of them hangs in connect(2) and will eventually error out because
