Hi
after the purge - install of fail2ban and logwatch yesterday
logwatch reported today that fail2ban made a new database for the
activities.
So reportung works again ootb.
Thank you for mental sparring
--
mit freundlichen Grüßen
with the beste regards
cordialement
Erich |\/|inderlei|\|
_
Hi all
Hi Ludovic
I found that monit is a backports package, not in standard install
both for debian and devuan
a case of PEBKAC
Thanks Dimitris
the command line logwatch yields a more detailed output than the cron.daily
I did that now
purging + reinstalling both logwatch and fail2ban
added nex
Στις 22/1/21 3:24 μ.μ., ο/η Erich Minderlein via Dng έγραψε:
Now I miss the section fail2ban in the logwatch daily mail
i don't use monit, just fail2ban and logwatch in some machines.
never had any issues with it.. neither in debian nor devuan machines .
usually set it up and forget about it..
Hi Erich,
On Fri, 2021-01-22 at 14:24 +0100, Erich Minderlein via Dng wrote:
> Hi
>
> I have migrated a small home server from debian buster to devuan
> beowulf.
> It was a new install, but I compared/copied /etc and copied the
> server /var/www
> It was rather flawless.
> However before the pack
Hello Erich,
I don't think either logwatch nor fail2ban is being forked by the folks
at debian. As such, you are using the debian packages. There may be
functionalities depending on systemd, but that's for you to discover.
In any case, what *exactly* is not part of devuan? Please provide a
link t
Hi
I have migrated a small home server from debian buster to devuan beowulf.
It was a new install, but I compared/copied /etc and copied the server /var/www
It was rather flawless.
However before the package monit was used as intermediate function beween
fail2ban and logwatch.
This is not part o
