You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Finally looking at upgrading our log-courier installations (2.0.6 -> 2.6.2).
We've got a rsyslog configuration, which sends 'log-courier' logs to a specific log file. Something like this:
But after upgrading this stopped working. The issue is that the progname is now a full path:
Before:
Sep 9 12:59:43 stankea log-courier[15511]: Loading registrar data from /var/run//.log-courier
Now:
Sep 9 13:50:54 stankea /usr/local/bin/log-courier[26304]: Loading registrar data from /var/run//.log-courier
And based on the documentation, the slash is a terminator, so the /usr/local/bin/log-courier becomes an empty progname:
Docs:
programname
the “static” part of the tag, as defined by BSD syslogd. For example, when TAG is “named[12345]”, programname is “named”.
Precisely, the programname is terminated by either (whichever occurs first):
end of tag
nonprintable character
‘:’
‘[‘
‘/’
Technically, it's probably not a bug, but a feature request :) Is it possible to have the log use basename($0) rather than the full path to the binary?
The text was updated successfully, but these errors were encountered:
Howdy,
Finally looking at upgrading our log-courier installations (2.0.6 -> 2.6.2).
We've got a rsyslog configuration, which sends 'log-courier' logs to a specific log file. Something like this:
But after upgrading this stopped working. The issue is that the progname is now a full path:
Before:
Now:
And based on the documentation, the slash is a terminator, so the
/usr/local/bin/log-courier
becomes an empty progname:Docs:
Technically, it's probably not a bug, but a feature request :) Is it possible to have the log use basename($0) rather than the full path to the binary?
The text was updated successfully, but these errors were encountered: