An errata patch for LibreSSL has been released for OpenBSD 6.8 and
OpenBSD 6.9.
Printing a certificate can result in a crash in X509_CERT_AUX_print().
Binary updates for the amd64, i386 and arm64 platform are available
via the syspatch utility. Source code patches can be found on the
respective
Shell aliases are good for that.
I think I'd be happy with 3 seconds by default. 2 feels a bit short on
overloaded links, GPRS, and some round-the-world packet trips
--
Sent from a phone, apologies for poor formatting.
On 20 August 2021 16:30:24 Tom Smyth wrote:
Hello all,,
would it make
Global configuration state for per-use commands is crazy.
Tom Smyth wrote:
> Hello all,,
> would it make sense
> to have the value as a sysctl option or an environment variable ?
> so that it can be tailored for users /admins needs,
>
>
>
> On Fri 20 Aug 2021, 12:22 Mark Kettenis,
Hello all,,
would it make sense
to have the value as a sysctl option or an environment variable ?
so that it can be tailored for users /admins needs,
On Fri 20 Aug 2021, 12:22 Mark Kettenis, wrote:
> > From: Florian Obser
> > Date: Fri, 20 Aug 2021 10:46:21 +0200
> >
> > Makes sense to
I am aware of (terrible) paths inside Canada which get close to 600ms.
I believe 1 second will make traceroute subtly fail to diagnose network
issues. I suspect 3 seconds might still work in the majority of cases,
but even 2 seconds seems too tight.
I remember many years ago when the
To whom may concern, one of the main spanish ADSL providers (because
rural connectivity is mainly ADSL over here) use interleaved FEC on
their devices. So expect 120 ms latency just in the last copper mile.
Add two poor WiFi hops, and 1 s may be too short at prime time.
Yep, my opinion is very
Hi
swapctl defaults to -l since 2007. This syncs the manpage synopsis with
the swapctl usage text.
Best,
Martin
diff --git a/sbin/swapctl/swapctl.8 b/sbin/swapctl/swapctl.8
index 10a76bd6c01..d447f8fee8d 100644
--- a/sbin/swapctl/swapctl.8
+++ b/sbin/swapctl/swapctl.8
@@ -49,7 +49,7 @@
.Fl d
I guess I was too optimistic.
I regularly work on machines that are 600-700 ms away and figured an additional
300 ms is good enough. Maybe not in case of congested links...
On 20 August 2021 13:17:12 CEST, Mark Kettenis wrote:
>> From: Florian Obser
>> Date: Fri, 20 Aug 2021 10:46:21 +0200
>>
> From: Florian Obser
> Date: Fri, 20 Aug 2021 10:46:21 +0200
>
> Makes sense to me, OK florian
Doesn't make sense to me. The RTT for an ICMP packet can be a
significant part of a second (think Europe-Australia the wrong way
around cause that is where all the bandwidth is, or when satellites
On 2021/08/20 10:46, Florian Obser wrote:
> Makes sense to me, OK florian
I think 1 second by default is still too short.
Makes sense to me, OK florian
On 2021-08-19 23:47 -07, wrote:
> The default traceroute timeout of 5 seconds is excruciatingly long
> when there are elements of the route that don't respond, and it
> wasn't allowed to be set lower than 2 seconds.
>
> This changes the minimum to 1 second, matching
The default traceroute timeout of 5 seconds is excruciatingly long
when there are elements of the route that don't respond, and it
wasn't allowed to be set lower than 2 seconds.
This changes the minimum to 1 second, matching FreeBSD, and also
makes that the default, which should be reasonable for
12 matches
Mail list logo
