> On Nov 29, 2018, at 9:15 AM, Robert Chalmers <racu...@gmail.com> wrote:
>
> I upgraded to and installed 3.4 today. It appears to be running, but all
> logging has stopped. The last entry in the log file was at the exact time I
> started the new version.
Apple changed the syslog API to use the os_log(3) interface, but apparently
if you compile on a sufficiently old MacOS/X system, you get linked against
the traditional syslog API.
So some people do that, but the os_log(3) stuff is configurable, so you
should be able to configure the logs to be saved. The in-memory logs
can be queried with log(1). For example:
# postfix reload
postfix/postfix-script: refreshing the Postfix mail system
# log show --info --style syslog --last 2m --predicate 'eventType ==
logEvent' | grep libpostfix-util
2018-11-29 12:02:26.765215-0500 localhost postlog[59348]:
(libpostfix-util.dylib) refreshing the Postfix mail system
2018-11-29 12:02:26.776443-0500 localhost master[33680]:
(libpostfix-util.dylib) reload -- version 3.4-20181125, configuration
/var/tmp/postfix/etc
Someone should figure out how create an asl.conf(5) configuration
that causes appropriate Postfix logs to land on disk, and share
the recipe.
I should note that the new API appears to strip everything up to
the last "/" in the log name, so we're losing the "postfix/"
prefixes. Might need to change the code (on MacOS) to send
postfix:master
rather than
postfix/master
--
Viktor.
