Simply omit conversions from timevals to hz and use the proper API.
First one is trivial, the second one truncates the converted number of
ticks to at leat one, which timeout_add_*(9) does automatically, so stop
doing it manually.
Tested by running it on my X230.
OK?
Index: kern_time.c
Hi Ingo,
Yes the usage of "truncate" and "chop" are unfortunate. I agree positive
language is always better.
Many thanks,
George
subscribe tech@openbsd.org
Hi George,
George Brown wrote on Sat, Jul 20, 2019 at 01:29:37PM +0100:
> When viewing a file with "less -S" that has lines longer than $COLUMNS
> said lines are simply not wrapped. The contents of said lines is still
> available, one simply needs to scroll horizontally. I would have
> expected
There are cases for ping(8)'s "-i wait" option that we don't handle
correctly.
Negative values smaller than -1:
$ doas ping -i -0.1 localhost
[no error]
Positive values less than one microsecond:
$ doas ping -i 0.001 localhost
[no error]
Large positive values that actually fit into a
When viewing a file with "less -S" that has lines longer than $COLUMNS
said lines are simply not wrapped. The contents of said lines is still
available, one simply needs to scroll horizontally. I would have
expected the contents displayed within less to be as if I had run
something like "cut -c
On Fri, Jul 19, 2019 at 02:15:03PM +0200, Jan Klemkow wrote:
> On Fri, Jul 19, 2019 at 09:13:38PM +1000, Jonathan Gray wrote:
> > On Fri, Jul 19, 2019 at 01:07:34PM +0200, Jan Klemkow wrote:
> > > Hi,
> > >
> > > fixstring() can return NULL and it does on one of my machines.
> > > Here is s fix
this adds a couple of lines to the lacp output so you can see what
params are used on the wire. this can help if you've put switchports in
different port-channels or such. an example of that is:
aggr0: flags=8847 mtu 1500
lladdr fe:e1:ba:d0:35:21
index 10 priority 0 llprio 7
