slaacd is started before syslogd. The behaviour of dropping it, rather than capturing it from the log buffer, is a bit odd.
Jason Mader <[email protected]> wrote: > >Synopsis: slaacd does not properly log messages (sendsyslog: dropped 1 > message, error 57) > >Category: system > >Environment: > > System : OpenBSD 6.7 > > Details : OpenBSD 6.7 (GENERIC.MP) #1: Sat May 16 16:33:02 MDT 2020 > > [email protected]:/usr/src/sys/arch/amd64/compile/ > GENERIC.MP > > > Architecture: OpenBSD.amd64 > > Machine : amd64 > > >Description: > > May 23 11:43:39 puffy sendsyslog: dropped 1 message, error 57, pid 74132 > > This is just "startup". > > >How-To-Repeat: > > puffy# /sbin/slaacd -d > > startup > > > Starting with verbose, slaacd_flags="-v", just results in, > > May 23 11:52:06 puffy sendsyslog: dropped 46 messages, error 57, pid 61509 > > >Fix: > > syslog should be logging that slaacd is starting up, with facility > daemon.info, > > May 23 11:43:39 puffy slaacd[74132]: engine ready
