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

On Aug 15, 2019, at 2:53 PM, Gerben Wierda wrote: > Now, that says that syslog messages also end up in Unified Logging. What it > doesn’t say how for instance old style messages for facility mail with level > notice end up there. Or with facility daemon with level info. So, how to get > these

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

> On 15 Aug 2019, at 17:48, Daniel J. Luke wrote: > > 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. I first thought: that

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

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

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

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