For ages I had used acme.sh sending logs into syslog using the following in /etc/syslog.conf:
So this stops a program name of acme.sh logging to any of the normal log files, and then redirects it into /var/log/acme.log.
This worked fine for years. However I've just noticed that it no longer works. I assume since various syslogd commits that happened through june/july in the stable tree for 11.x (I'm running 11.2-STABLE).
If I test with this command, it fails to log anything:
If I test with this command (and change the syslog.conf to suit) then it logs everything as expected:
So it looks like syslogd is now treating program specifications with a . character in them differently to how it was before. I guess it may be problematic because that's usually how you specify the facility.priority. But it used to work fine......
I've tried escaping the . with a \ and putting quotes around it etc. Doesn't seem to make any difference. Any ideas? Am I missing how you need to configure this, or is it a bug?
Code:
!-acme.sh
... normal syslog.conf entries ...
!acme.sh
*.* /var/log/acme.log
!*
So this stops a program name of acme.sh logging to any of the normal log files, and then redirects it into /var/log/acme.log.
This worked fine for years. However I've just noticed that it no longer works. I assume since various syslogd commits that happened through june/july in the stable tree for 11.x (I'm running 11.2-STABLE).
If I test with this command, it fails to log anything:
logger -p user.err -t acme.sh test message
If I test with this command (and change the syslog.conf to suit) then it logs everything as expected:
logger -p user.err -t acme test message
So it looks like syslogd is now treating program specifications with a . character in them differently to how it was before. I guess it may be problematic because that's usually how you specify the facility.priority. But it used to work fine......
I've tried escaping the . with a \ and putting quotes around it etc. Doesn't seem to make any difference. Any ideas? Am I missing how you need to configure this, or is it a bug?