store nd6 expiries in the rtentry

this makes it consistent with arp, where route get has the right expiry. note that you cannot have an nd6 llinfo thing without an associated rtentry, so nd_rt is always safe to deref. ok? Index: nd6.c === RCS file:

Re: kdump small timespecs

Ted Unangst wrote: > Philip Guenther wrote: > > I think it would be better to include the clock_t value in the > > timespec struct tracing, then branch on that. > > I of course looked at that, but it's a lot of plumbing... If there is no serious objection, I'd like to go ahead with this version,

Re: Fix uvm bug

Oh, I think I've been here before.. on sparc.. with buffer cache stuff.. yes please. On Thu, Jun 02, 2016 at 10:55:24PM +0200, Mark Kettenis wrote: > The fix below fixes the following panic that mglocker@ was seeing on > macppc: > > panic: uvm_addr_invoke: address selector 0xfe8000

Re: Website HTTPS

Indeed. that is why we do not reccomend you use http://openbsd.org/ On Thu, Jun 02, 2016 at 11:22:37AM -0400, Robert Tate wrote: > It looks like the cert used when you access the site with openbsd.org > is only good for www.openbsd.org and so browsers will give warnings > when accessing

Re: wifind(8) find your wifi

On Thu, Jun 2, 2016 at 7:52 PM, Mike Belopuhov wrote: > On 3 June 2016 at 00:17, Gleydson Soares wrote: >> I usually just use a small script that lives in ~/bin >> > > It's a great name, though. Oops, Disregard it... it was a reply to:

wifind(8) find your wifi

I usually just use a small script that lives in ~/bin cat ~/bin/wifi #!/bin/sh if [[ $1 == "home" ]]; then doas ifconfig run0 nwid foonet wpa wpakey ultrasecret doas dhclient run0 fi

Fix uvm bug

The fix below fixes the following panic that mglocker@ was seeing on macppc: panic: uvm_addr_invoke: address selector 0xfe8000 (uaddr_bestfit 0xe000-0xee00) returned unavailable address 0xe8a59000 This happened immediately after a failed malloc(9). What is happening here is that we

pcmcia unused function diff

Hello - Remove unused functions. Index: dev/pcmcia/pcmcia.c === RCS file: /cvs/src/sys/dev/pcmcia/pcmcia.c,v retrieving revision 1.46 diff -u -p -r1.46 pcmcia.c --- dev/pcmcia/pcmcia.c 8 Oct 2012 21:47:50 - 1.46 +++

Re: Website HTTPS

Robert Tate wrote: > It looks like the cert used when you access the site with openbsd.org > is only good for www.openbsd.org and so browsers will give warnings > when accessing https://openbsd.org/. So don't access https://openbsd.org/?

Website HTTPS

It looks like the cert used when you access the site with openbsd.org is only good for www.openbsd.org and so browsers will give warnings when accessing https://openbsd.org/.

[patch] adding quotes for space-containing values in smtpd(8) logs

Dear all, Could you consider quoting the space-containing values in smtpd log messages? I like the latest smtpd log format improvements, but it's hard to parse space-separated key-value pairs if they have space-containing values :) Please see the patch attached. -- With best regards, Pavel

PF error message tweak

The below error message sequence isn't as clear as it could be: > mike:/home/mike$ doas pfctl -f /etc/pf. > pfctl: /etc/pf.: No such file or directory > pfctl: cannot open the main config file!: No such file or directory > pfctl: Syntax error in config file: pf rules not loaded There are

Re: Packet loss on traffic flowing between VLANs

Hi Evgeniy, Thank you for your reply. The states hard limit was the problem. The default limit is quite low :) -- Tim Korn Network Ninja On Thu, Jun 2, 2016 at 3:48 AM, Evgeniy Sudyr wrote: > Tim, > > from your problem description I can suggest you to check

Re: Packet loss on traffic flowing between VLANs

Tim, from your problem description I can suggest you to check if you are not hitting states hard limit with (note - during load when you can reproduce issue): pfctl -si pfctl -sm Default limit is: stateshard limit1 -- Evgeniy On Thu, Jun 2, 2016 at 3:29 AM, Tim Korn

Re: video(1) munmap fix

On Thu, Jun 02, 2016 at 09:33:55AM +0200, Marcus Glocker wrote: > On Thu, Jun 02, 2016 at 09:10:11AM +0200, Sebastien Marie wrote: > > > On Thu, Jun 02, 2016 at 08:54:35AM +0200, Marcus Glocker wrote: > > > Just try to unmap a buffer when something has been mapped before. > > > > > > ok? > > >

Re: video(1) munmap fix

On Thu, Jun 02, 2016 at 09:10:11AM +0200, Sebastien Marie wrote: > On Thu, Jun 02, 2016 at 08:54:35AM +0200, Marcus Glocker wrote: > > Just try to unmap a buffer when something has been mapped before. > > > > ok? > > Personnally, I would enclose the if (r == -1) inside the test for NULL: > it

Re: video(1) munmap fix

On Thu, Jun 02, 2016 at 08:54:35AM +0200, Marcus Glocker wrote: > Just try to unmap a buffer when something has been mapped before. > > ok? Personnally, I would enclose the if (r == -1) inside the test for NULL: it seems odd to test the r value if you didn't call munmap on it, and its value was

video(1) munmap fix

Just try to unmap a buffer when something has been mapped before. ok? Index: video.c === RCS file: /cvs/xenocara/app/video/video.c,v retrieving revision 1.14 diff -u -p -u -p -r1.14 video.c --- video.c 31 May 2016 08:45:14