Date: Sun, 30 Sep 2018 13:16:52 +0300 From: Pavel Timofeev <timp87@gmail.com> To: freebsd-hackers@freebsd.org Subject: Re: Syslogd less verbose logging with rfc5424 Message-ID: <CAAoTqfv%2BbAsLuXefb3apoPYO25L860Q%2B7fYnz0a0R=-MC0T5dA@mail.gmail.com> In-Reply-To: <CAAoTqftD3w62j5gxew4s9ZCzgc-zkDEqpMLUQ7fK%2B6jqL3oDfw@mail.gmail.com> References: <CAAoTqftD3w62j5gxew4s9ZCzgc-zkDEqpMLUQ7fK%2B6jqL3oDfw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Hello, dear community! > > There was a great work to bring rfc5424 date format to syslogd(8). See > https://svnweb.freebsd.org/base?view=revision&revision=332510 > > I've been using it on CURRENT since it was imported. > I'm happy I can finally get syslog messages with high time precision > w/o installing rsyslog or another syslog implementation. > The thing I really don't like is that syslogd puts severity and > priority to log files next to timestamp. > In my opinion severity and priority is not needed in 99% of cases, > only in debugging corner cases. While high precision timestamp is the > main thing what people like rfc 5424 for. This is just my opinion. > So for "-O rfc5424" I'd like to have the same behavior as for rfc > 3164, i. e. do not log severity and priority by default and if needed > use '-v' option to enable those. But it was decided and documented > that '-v' won't have any effect for rfc 5425 > https://svnweb.freebsd.org/base?view=revision&revision=335862 > > The first thing I'd like to suggest is to make rfc 5424 logging the > same way as for rfc 3164, i. e. make '-v' option work the same. > If community is not agree with me, I'd like to suggest another thing: > have another option/flag for syslogd(8) to disable severity and > priority logging if one use rfc 5424. Just for visibility this is how /var/log/message log looks like now if I enable rfc 5424 logging: <2>1 2018-09-30T13:13:14.105894+03:00 nostromo kernel - - - #8 0xffffffff8105f82c at amd64_syscall+0x28c <2>1 2018-09-30T13:13:14.105901+03:00 nostromo kernel - - - #9 0xffffffff8103c14d at fast_syscall_common+0x101 <2>1 2018-09-30T13:13:14.105912+03:00 nostromo kernel - - - Security policy loaded: MAC/ntpd (mac_ntpd) <101>1 2018-09-30T13:13:14.124700+03:00 nostromo ntpd 937 - - ntpd 4.2.8p12-a (1): Starting <101>1 2018-09-30T13:13:14.224314+03:00 nostromo ntpd 938 - - leapsecond file ('/var/db/ntpd.leap-seconds.list'): good hash signature <101>1 2018-09-30T13:13:14.224570+03:00 nostromo ntpd 938 - - leapsecond file ('/var/db/ntpd.leap-seconds.list'): loaded, expire=2018-12-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37 <13>1 2018-09-30T13:13:14.391787+03:00 nostromo root 990 - - /etc/rc: WARNING: $dbus_enable is not set properly - see rc.conf(5). <28>1 2018-09-30T13:13:14.640885+03:00 nostromo avahi-daemon 1038 - - WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAAoTqfv%2BbAsLuXefb3apoPYO25L860Q%2B7fYnz0a0R=-MC0T5dA>