When originally writing snmp(1) I wanted to stay as close to netsnmp as
possible to make sure I didn't introduce anything I would regret.
Now that 6.6 is out the door and I'm feeling more comfortable with the
tool I want to start being a little more lenient. Here's a first step by
allowing the -C
On Mon, 28 Oct 2019, Damien Miller wrote:
> BTW, the token still becomes unresponsive after the first transaction,
> but looking at a sniff (using an OpenViszla), it seems we're getting the
> DATA0/DATA1 flipping incorrect on the wire.
>
> On OpenBSD, this is the last rx of the transaction with t
On Sat, Oct 26, 2019 at 12:57:56AM +0200, Klemens Nanni wrote:
> It makes no sense to allow zero interfaces; either a positive count is
> given or -i is omitted entirely. vm.conf(5) does not allow interface
> configuration that results in zero interfaces either.
>
> $ doas vmctl start -Li0
Index: errata66.html
===
RCS file: /cvs/www/errata66.html,v
retrieving revision 1.2
diff -u -p -u -r1.2 errata66.html
--- errata66.html 27 Oct 2019 20:01:00 - 1.2
+++ errata66.html 27 Oct 2019 22:07:59 -
@@ -67
On Fri, 25 Oct 2019, Patrick Wildt wrote:
> > So from what I understood the Yubikey expects the transfer to happen
> > on the Interrupt OUT pipe instead of doing a control transfer. Read-
> > ing some code and documentation, it looks like that we should by de-
> > fault send our reports on the in
In version 1.78 of /etc/daily, the -i flag was added to the df output.
Apparently, some people run out of inodes.
I only seem to run out of disk space, and too often, my eye skims
the daily report from a machine, looks at the last column,sees a
small percentage, and I decide, "all is good", even i
On Sat, Oct 19 2019, tho...@habets.se wrote:
> On Sat, 19 Oct 2019 16:32:56 +0100, Jeremie Courreges-Anglas
> said:
>> > Before:
>> > $ HISTSIZE=10 /bin/sh
>> > /bin/sh: internal error: unable to allocate memory
>> > <--- no ksh
>> Could you provide more details please? A fatal
