>
> On Aug 22, 2017 at 1:18 PM, <Florian Obser> wrote:
>
>
> On Tue, Aug 22, 2017 at 08:06:08PM +0200, Christer Solskogen wrote: > On
> Tue, Aug 22, 2017 at 4:01 PM, Florian Obser wrote: > > > On Tue, Aug
> 22, 2017 at 01:56:10PM +0200, Christer Solskogen wrote: > > > Running
> the latest snapshot (amd64) I see that slaacd.sock is in /dev, > > >
> while documentation says that is should be in /var/run. What is correct? >
> > > > Friend Computer is of course right. Just fixed the man page.
> Thanks! > > > > > I probably haven't got myself enough covfefe
> today, so I'm a bit off when > it comes to the jargon here. > But is /dev
> really the correct place? And what is Friend Computer? :) See
> https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sbin/slaacd/slaacd.h#rev1.2:
> --- We are going to start slaacd(8) much earlier, before /var is even
> mounted. Move control socket to /dev for now. Input & OK deraadt@ --- There
> are not that many places where we can put the control socket that early in
> the boot process. Also https://cv
sweb.openbsd.org/cgi-bin/cvsweb/src/etc/rc#rev1.501 The idea is to have working
v6 as early as possible so that daemons like ntpd and unbound can use it. We
have not succeded fully though. ntp tends to ignore v6 if it's not available
when ntp comes up but you later get v6. This might actually be a problem that
needs to be fixed in ntpd. Friend Computer:
https://en.wikipedia.org/wiki/Paranoia_(role-playing_game)
>
>
> Looks interesting, but oop apparently.
>
> > > -- > chs -- I'm not entirely sure you are real.
>
