| Summary: | app-admin/syslog-ng-3.5.1 version bump | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | RumpletonBongworth <kfm> |
| Component: | Current packages | Assignee: | Mr. Bones. (RETIRED) <mr_bones_> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://asylum.madhouse-project.org/blog/2013/09/05/what-is-cooking-in-syslog-ng-3.5/ | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Apologies. I meant to say that it should still choose file("/proc/kmsg") in the case of older kernels.
|
As per the summary, the next major release of syslog-ng is available. One of the many new features is that the superior /dev/kmsg interface is supported for the collection of messages, which works with Linux 3.5 or newer. If you haven't done so already, you should consider switching to declaring system() so that syslog-ng is allowed to pick the optimal interface, rather than hard-coding the particulars in the syslog-ng.conf file that you distribute. For kernels older than 3.5, it should still choose to use unix-dgram("/dev/log").