Date: Sun, 17 Dec 2017 16:41:29 -0500 From: Michael Butler <imb@protected-networks.net> To: Ben Woods <woodsb02@gmail.com>, Baptiste Daroussin <bapt@freebsd.org> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: what's changed with newsyslog? Message-ID: <d9b44a60-de2c-84a6-2262-f093e6a8c454@protected-networks.net> In-Reply-To: <CAOc73CDxv66zUn8RcGA3teA=6wiHLDHsHvyJu2S5FF2ZQQz%2BCw@mail.gmail.com> References: <7c79c676-3414-8cab-bcf8-b3e3d08a70f6@protected-networks.net> <CAOc73CDxv66zUn8RcGA3teA=6wiHLDHsHvyJu2S5FF2ZQQz%2BCw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/17/17 16:38, Ben Woods wrote: > On Mon, 18 Dec 2017 at 3:47 am, Michael Butler > <imb@protected-networks.net <mailto:imb@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d9b44a60-de2c-84a6-2262-f093e6a8c454>