On 2017/09/07 16:40, Theo de Raadt wrote:
> > On Thu, Sep 07, 2017 at 12:05:11PM +0200, Sebastian Benoit wrote:
> > > The reason you see the message on the console on halt and reboot is,
> > > because
> > > syslogd is gone at that point, so the message goes to the console instead.
> >
> >
> On Thu, Sep 07, 2017 at 12:05:11PM +0200, Sebastian Benoit wrote:
> > The reason you see the message on the console on halt and reboot is, because
> > syslogd is gone at that point, so the message goes to the console instead.
>
> pflogd(8) explicitly requests this behavior.
>
>
On Thu, Sep 07, 2017 at 01:16:18PM +0200, Alexander Bluhm wrote:
> On Thu, Sep 07, 2017 at 12:05:11PM +0200, Sebastian Benoit wrote:
> > The reason you see the message on the console on halt and reboot is, because
> > syslogd is gone at that point, so the message goes to the console instead.
>
>
On Thu, Sep 07, 2017 at 12:05:11PM +0200, Sebastian Benoit wrote:
> The reason you see the message on the console on halt and reboot is, because
> syslogd is gone at that point, so the message goes to the console instead.
pflogd(8) explicitly requests this behavior.
Bryan Steele(bry...@openbsd.org) on 2017.09.05 16:17:46 -0400:
> pflogd(8) currently spams the console on shutdown if syslogd wins the
> race to die, this logging probably comes from the fact that pflogd was
> largely based on syslogd.
i looked at that some time ago: a and found that lot of our
