On Tue, 20 Sep 2022 08:50:10 +0200, Florian Obser wrote:
> Is this somehow coming from the non-blocking connect diff? I can't spot
> it though...
I don't think so, the ktrace shows that read(2) is returning 0 long
after connect. If the socket was left in non-blocking mode I could
see that
Florian Obser wrote:
> On 2022-09-19 22:27 +02, Hrvoje Popovski wrote:
> > Hi all,
> >
> > when doing sysupgrade few minutes ago on multiple machines i'm getting
> > error in subject
> >
> > smc24# sysupgrade -s
> > Fetching from https://cdn.openbsd.org/pub/OpenBSD/snapshots/amd64/
> >
On 20.9.2022. 8:50, Florian Obser wrote:
> On 2022-09-19 22:27 +02, Hrvoje Popovski wrote:
>> Hi all,
>>
>> when doing sysupgrade few minutes ago on multiple machines i'm getting
>> error in subject
>>
>> smc24# sysupgrade -s
>> Fetching from https://cdn.openbsd.org/pub/OpenBSD/snapshots/amd64/
On 2022-09-19 22:27 +02, Hrvoje Popovski wrote:
> Hi all,
>
> when doing sysupgrade few minutes ago on multiple machines i'm getting
> error in subject
>
> smc24# sysupgrade -s
> Fetching from https://cdn.openbsd.org/pub/OpenBSD/snapshots/amd64/
> SHA256.sig 100%
On 19.9.2022. 22:27, Hrvoje Popovski wrote:
> Hi all,
>
> when doing sysupgrade few minutes ago on multiple machines i'm getting
> error in subject
>
> smc24# sysupgrade -s
> Fetching from https://cdn.openbsd.org/pub/OpenBSD/snapshots/amd64/
> SHA256.sig 100%
Hi all,
when doing sysupgrade few minutes ago on multiple machines i'm getting
error in subject
smc24# sysupgrade -s
Fetching from https://cdn.openbsd.org/pub/OpenBSD/snapshots/amd64/
SHA256.sig 100% |*|
2144 00:00
Signature Verified
