Re: what's changed with newsyslog?
On Sun, Dec 17, 2017 at 04:41:29PM -0500, Michael Butler wrote: > On 12/17/17 16:38, Ben Woods wrote: > > On Mon, 18 Dec 2017 at 3:47 am, Michael Butler > > mailto:i...@protected-networks.net>> wrote: > > > > In the past week or so I've been getting warnings like this .. > > > > bzip2: Can't open input file /var/log/snmpd.log.0: No such file or > > directory. > > newsyslog: `/usr/bin/bzip2 -f /var/log/snmpd.log.0 > > /var/log/fwlw_clean_log.0' terminated with a non-zero status (1) > > [ .. snip .. ] > > > > > > > Hints? > > > > imb > > > > Could this be related to bapt’s recent change 11 days ago to allow > > newsyslog to use different style of compression commands? > > https://svnweb.freebsd.org/base?view=revision&revision=326617 > > Yes - I reverted to r326616 and the issue no longer appears, > > imb > Should be fixed in r326930, sorry about that Best regards, Bapt signature.asc Description: PGP signature
Re: what's changed with newsyslog?
On 12/17/17 16:38, Ben Woods wrote: > On Mon, 18 Dec 2017 at 3:47 am, Michael Butler > mailto:i...@protected-networks.net>> wrote: > > In the past week or so I've been getting warnings like this .. > > bzip2: Can't open input file /var/log/snmpd.log.0: No such file or > directory. > newsyslog: `/usr/bin/bzip2 -f /var/log/snmpd.log.0 > /var/log/fwlw_clean_log.0' terminated with a non-zero status (1) [ .. snip .. ] > > > Hints? > > imb > > Could this be related to bapt’s recent change 11 days ago to allow > newsyslog to use different style of compression commands? > https://svnweb.freebsd.org/base?view=revision&revision=326617 Yes - I reverted to r326616 and the issue no longer appears, imb ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: what's changed with newsyslog?
On Mon, 18 Dec 2017 at 3:47 am, Michael Butler wrote: > In the past week or so I've been getting warnings like this .. > > bzip2: Can't open input file /var/log/snmpd.log.0: No such file or > directory. > newsyslog: `/usr/bin/bzip2 -f /var/log/snmpd.log.0 > /var/log/fwlw_clean_log.0' terminated with a non-zero status (1) > > I've checked the relevant /etc/newsyslog.conf and its /usr/local/etc > counterpart to ensure there are tabs in the right places but the errors > persist. > > Similarly, the relevant files are there and seem to be rotated as > expected/desired .. > > -rw-r--r-- 1 root wheel 77 Dec 17 09:00 fwlw_clean_log > -rw-r--r-- 1 root wheel 11282 Dec 17 09:00 fwlw_clean_log.0.bz2 > -rw-r--r-- 1 root wheel 9452 Dec 17 05:00 fwlw_clean_log.1.bz2 > > [ .. ] > > -rw-r--r-- 1 root wheel 50992 Dec 17 09:45 snmpd.log > -rw-r--r-- 1 root wheel 1834 Dec 17 09:00 snmpd.log.0.bz2 > -rw-r--r-- 1 root wheel 1846 Dec 17 07:00 snmpd.log.1.bz2 > > > Hints? > > imb > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" Could this be related to bapt’s recent change 11 days ago to allow newsyslog to use different style of compression commands? https://svnweb.freebsd.org/base?view=revision&revision=326617 Regards, Ben -- -- From: Benjamin Woods woods...@gmail.com ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"