syslog-ng Development Reports
-
Peter 'CzP' Czanik ☛ The syslog-ng Insider 2024-01: HTTP; Clownflare; systemd-journal; Humio / Logscale;
The January syslog-ng newsletter is now on-line: [...]
-
Peter 'CzP' Czanik ☛ Native MacOS source in syslog-ng
You know that support for MacOS is important when every third visitor at the syslog-ng booth of Red Bait Summit asks if syslog-ng works on MacOS. With the upcoming syslog-ng version 4.6.0, syslog-ng not only compiles on MacOS, but it also collects local log messages natively. From this blog you can learn how to compile syslog-ng yourself, options of the MacOS source, and also a bit of history.
-
Peter Czanik: Native MacOS source in syslog-ng
From this blog you can learn how to compile syslog-ng yourself, options of the MacOS source, and also a bit of history.
Many years ago, syslog-ng was available on MacOS. It was even part of Homebrew. Unfortunately, when multi-threading was introduced to syslog-ng in version 3.3, it broke MacOS support. It was not syslog-ng directly, but the file naming convention of a new mandatory dependency (the file system is case-insensitive on MacOS). Supporting MacOS again took a bit more time than expected. The external library had to be fixed first, which meant renaming files. Once it was fixed, syslog-ng could also be brought back to life on MacOS.
Syslog-ng compiled and ran fine on MacOS, however it could not collect local system logs natively. It could act as a network server or read files on the system. The default configuration failed to start, as the system() source was not configured for MacOS. As a workaround, a system() source was defined on MacOS too: it simply reads files written by the native syslogd. Syslog-ng is now part of Homebrew again, which means easy installation. With version 4.6.0, syslog-ng can collect local system logs natively.