Date: Thu, 12 Jul 2018 20:22:54 +0100 From: Matt Smith <matt.xtaz@gmail.com> To: Eugene Grosbein <eugen@grosbein.net> Cc: freebsd-stable@freebsd.org Subject: Re: syslogd not logging with . in program name Message-ID: <20180712192254.GB41523@gmail.com> In-Reply-To: <5B47A7E0.1060308@grosbein.net> References: <20180712181411.GA41523@gmail.com> <5B47A7E0.1060308@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 13 02:11, Eugene Grosbein wrote: >13.07.2018 1:14, Matt Smith wrote: > >> I run acme.sh with it configured to log to syslog. I use this syslog.conf structure to log to a specific log file: >> >> !-acme.sh >> ... other syslog.conf entries ... >> !acme.sh >> *.* /var/log/acme.log >> !* >> >> This has worked for ages, but I've just noticed it's no longer working at all. It appears that syslogd is now not happy with a . character in a program name. I see that there have been a lot of commits to syslogd during June and July which may have changed the behavior? >> >> If I run logger -p user.err -t acme.sh test message then nothing is logged. If I run logger -p user.err -t acme test message (removing the .sh), with the same change in syslog.conf, then everything is logged as normal. >> >> Obviously . is used to separate facility and priority. Is it now being parsed wrongly in the case of a program name? I've tried things like putting it in quotes or escaping it with \ and it doesn't make any difference. > >You have not specified which version/revision you run. Whoops. My bad! It's 11.2-STABLE r336013. I'm not sure when this stopped working as I've only just noticed today but I usually do a buildworld every week. I took a look at svn log /usr/src/usr.sbin/syslogd though and can see there are quite a few updates in the last couple of months. -- Matt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180712192254.GB41523>