Logging to syslog (by unbound, nsd, etc.) disappearing in a black hole

[Daniel J. Luke]

High Sierra switched the way syslog works on Mac OS (see https://developer.apple.com/documentation/os/logging). This replaced the ASL (and syslog) stuff.

you can use the 'log' command line utility to view the logs.

[I am not a fan of the way this stuff works now]

> On Aug 15, 2019, at 3:46 AM, Gerben Wierda <gerben.wierda at rna.nl> wrote:
> 
> I’m running unbound. If I use file logging, it neatly ends up in the file I want. If I set syslog in the conf file (this is standard in macports unbound by the way) I get nothing. Logging disappears into a black hole, probably the same black hole where mail logging from postfix disappears in on High Sierra Server.
> 
>        use-syslog: <yes or no>
>               Sets unbound to send log messages to  the  syslogd,  using  sys-
>               log(3).   The  log  facility  LOG_DAEMON  is used, with identity
>               "unbound".  The logfile setting is overridden when use-syslog is
>               turned on.  The default is to log to syslog.
> 
> How do I make sure that I get to see the syslog messages. Probably by adapting /etc/asl.conf and /etc/syslog.conf? Or is it a matter of ASL hiding these kinds of messages from ordinary users? Is there a way to tell asl/syslog to put the logging output of unbound into a (log rotated) file in e.g. /var/log?
> 
> PS. Apple is apparently playing around with unbound too:
> 
> luna:~ gerben$ ls -l /usr/share/man/man8/unbound.8 
> -rw-r--r--  1 root  wheel  2342 Aug 23  2018 /usr/share/man/man8/unbound.8

-- 
Daniel J. Luke