Hi,
On Thu, Mar 14, 2024 at 04:18:26PM -0600, Charles Curley wrote:
> Interesting. My logcheck instance works just fine, andmakes no such
> complaints. However, my
> /etc/logcheck/logcheck.logfiles.d/syslog.logfiles has them commented
> out.
You are probably using the journald support as configur
On Thu, 14 Mar 2024 11:25:52 -0700
cono...@panix.com (John Conover) wrote:
> Email from logcheck(1) contains:
>
> E: File could not be read: /var/log/syslog
> E: File could not be read: /var/log/auth.log
>
> which do not exist in bookworm 12.5.
>
> The offending file:
>
> /etc/logc
Hi,
On Thu, Mar 14, 2024 at 11:25:52AM -0700, John Conover wrote:
> Email from logcheck(1) contains:
>
> E: File could not be read: /var/log/syslog
> E: File could not be read: /var/log/auth.log
>
> which do not exist in bookworm 12.5.
>
> The offending file:
>
> /etc/logcheck/logc
John Conover wrote:
>
> Email from logcheck(1) contains:
>
> E: File could not be read: /var/log/syslog
> E: File could not be read: /var/log/auth.log
>
> which do not exist in bookworm 12.5.
They do as soon as you install rsyslog.
Arguably this should be in rsyslog's package, though
On Thu, Mar 14, 2024 at 11:25:52AM -0700, John Conover wrote:
>
> Email from logcheck(1) contains:
>
> E: File could not be read: /var/log/syslog
> E: File could not be read: /var/log/auth.log
>
> which do not exist in bookworm 12.5.
You'll want to install rsyslog, or something equivale
Email from logcheck(1) contains:
E: File could not be read: /var/log/syslog
E: File could not be read: /var/log/auth.log
which do not exist in bookworm 12.5.
The offending file:
/etc/logcheck/logcheck.logfiles.d/syslog.logfiles
contains both filenames.
Thanks,
John
--
6 matches
Mail list logo
