Mavericks syslog server configuration

For you OS X server admins out there, the syntax to enable syslogd to act as a syslog server has changed under Mavericks and OS X Server v3.

As before, convert the plist from binary into xml using plutil:

sudo plutil -convert xml1 /System/Library/LaunchDaemons/com.apple.syslogd.plist

The open the plist in your favorite editor and look for <key>Sockets</key>. The \<dict\> block after this key holds the information that used be in the dict block following <key\>NetworkListener</key>, except now the information goes in a sub-block called BSDSystemLogger. The default BSDSystemLogger block looks like this:

<key>BSDSystemLogger</key>
<dict>
        <key>SockPathMode</key>
        <integer>438</integer>
        <key>SockPathName</key>
        <string>/var/run/syslog</string>
        <key>SockType</key>
        <string>dgram</string>
</dict>

This creates a UNIX socket in /var/run. To enable remote logging, we want a network socket on the syslog port. To get that, simply change the above block to this:

<key>BSDSystemLogger</key>
<dict>
        <key>SockType</key>
        <string>dgram</string>
        <key>SockServiceName</key>
        <string>syslog</string>
</dict>

Save the plist. You can re-convert it to binary if you like or just leave it in XML. Unload and reload the plist and syslog will start and accept remote syslog data.

2 thoughts on “Mavericks syslog server configuration

    1. dwight Post author

      Florian,

      My Leitra comes straight from Carl Georg himself. I’ve owned it for four years and ride it all winter as my “daily driver” went working on campus.

      The WildOne looks quite nice. How do you like the front suspension? Does it move enough to interfere with your legs when pedaling?

Comments are closed.