Re: dangling SEE ALSO references and some peculiarities in man pages

On Tue, Apr 30, 2019 at 12:16:10AM +0200, Marc Espie wrote: > On Sun, Apr 28, 2019 at 02:16:23PM -0500, Tim Chase wrote: > > Dangling SEE ALSO references to man-pages that don't exist: > > > > dig(1) references missing named(8) and dnssec-keygen(8) > > host(1) references missing named(8) > >

Re: dangling SEE ALSO references and some peculiarities in man pages

Marc Espie wrote: > On Sun, Apr 28, 2019 at 02:16:23PM -0500, Tim Chase wrote: > > Dangling SEE ALSO references to man-pages that don't exist: > > > > dig(1) references missing named(8) and dnssec-keygen(8) > > host(1) references missing named(8) > > nslookup(1) references missing named(8) > >

Re: dangling SEE ALSO references and some peculiarities in man pages

On Sun, Apr 28, 2019 at 02:16:23PM -0500, Tim Chase wrote: > Dangling SEE ALSO references to man-pages that don't exist: > > dig(1) references missing named(8) and dnssec-keygen(8) > host(1) references missing named(8) > nslookup(1) references missing named(8) > info(5) references missing

Re: panic: Stopped at kqueue_scan

> On 30 Apr 2019, at 03:24, Martin Pieuchot wrote: > > On 29/04/19(Mon) 17:24, David Gwynne wrote: >> On Sun, Apr 28, 2019 at 06:57:02PM -0300, Martin Pieuchot wrote: >>> On 23/04/19(Tue) 12:16, Olivier Antoine wrote: > Synopsis:panic: Stopped at kqueue_scan > Category:kernel

Re: panic: Stopped at kqueue_scan

With this diff, I haven't had a crash yet. Usually I plant in less than 2 minutes, with this patch, after 30 intensive minutes it still holds. On Mon, Apr 29, 2019 at 9:24 AM David Gwynne wrote: > > On Sun, Apr 28, 2019 at 06:57:02PM -0300, Martin Pieuchot wrote: > > On 23/04/19(Tue) 12:16,

Re: panic: Stopped at kqueue_scan

With this diff, either it crash the same way as before either it freeze completely, no output, no keyboard. I tried a dozen times without success.

"infinite" gethostbyname(3)

When my machine doesn't get a reply from a DNS server, generally the wifi router of the place where I'm drinking coffee, applications sit in gethostbyname(3) "indefinitely". At least too long for me to wait and I end up killing the app. $ cat /etc/resolv.conf # Generated by iwm0

Re: panic: Stopped at kqueue_scan

On 29/04/19(Mon) 17:24, David Gwynne wrote: > On Sun, Apr 28, 2019 at 06:57:02PM -0300, Martin Pieuchot wrote: > > On 23/04/19(Tue) 12:16, Olivier Antoine wrote: > > > >Synopsis:panic: Stopped at kqueue_scan > > > >Category:kernel i386 > > > >Environment: > > > System : OpenBSD

Re: Wireless failed when a space is present in SSID

On Sun, Apr 28, 2019 at 09:00:09AM +0200, j...@bistruphave.dk wrote: > >Synopsis:Wireless failed when a space is present in SSI > >Category:Wireless > >Environment: > System : OpenBSD 6.5 > Details : OpenBSD 6.5 (GENERIC) #1338: Sat Apr 13 15:07:04 MDT 2019 >

Re: iwm: unhandled firmware response

On Mon, Apr 29, 2019 at 02:10:26AM +0200, Krystian Lewandowski wrote: > I did use kern.bufcachepercent=90 before. I think I copied it blindly > from some blog post about OpenBSD on a laptop. No problems observed > for now with "iwm" since 20% value in use. The problem does not affect all

Re: panic: Stopped at kqueue_scan

On Sun, Apr 28, 2019 at 06:57:02PM -0300, Martin Pieuchot wrote: > On 23/04/19(Tue) 12:16, Olivier Antoine wrote: > > >Synopsis:panic: Stopped at kqueue_scan > > >Category:kernel i386 > > >Environment: > > System : OpenBSD 6.5 > > Details : OpenBSD 6.5-current (GENERIC.MP)

Wireless failed when a space is present in SSID

>Synopsis: Wireless failed when a space is present in SSI >Category: Wireless >Environment: System : OpenBSD 6.5 Details : OpenBSD 6.5 (GENERIC) #1338: Sat Apr 13 15:07:04 MDT 2019