Hi
Now I upgraded my other notebook from buster to beowulf.
No more debian systems chez moi.
I followed the advice from the website.
However, the upgrades of the notebooks were not smooth.
On the 2nd NB when I started the system after the dist-upgrade,
it went straight into the Xserver.
Only the
Hi
tonight my ansible stopped execution with the message
TASK [Reboot the box if kernel updated]
fatal: [*$Hostname*]: FAILED! => {"changed": false, "elapsed": 0, "msg": "Running reboot with
local connection would reboot the control node.", "rebooted": f
Hi all
currently I operate one server with devuan beowulf and
2 Notebooks with debian buster.
Migration is pending to devuan, as soon as a necessity arises, e.g. buster is
becoming oldstable.
Off Topic : the necessity has arisen now, as systemd produces huge
logfiles, 0,9 GByte in 10 hou
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
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
