Hi devs,
I am sorry to be troubling you with what may be a waste of your
valuable time, but I have a couple of questions for the list.  Following
on from the clamav-daemon problematic uninstallation, posted here
I have seen the following code in
both /etc/logrotate.d/clamav-daemon.dpkg-old
and /etc/logrotate.d/clamav-freshclam. 

/var/log/clamav/freshclam.log {
     rotate 12
     create 640  clamav adm
     if [ -d /run/systemd/system ]; then
         systemctl -q is-active clamav-freshclam && systemctl kill
--signal=SIGHUP clamav-freshclam || true else
         /etc/init.d/clamav-freshclam reload-log > /dev/null || true

But this code is not in any of the 16 other logrotate files in this
folder. I do not fully understand it, and so my first
question is are there any suggestions why it is there and why isn't it
necessary in the other files? I ask because I have uncovered an alarming
number of systemd files throughout the computer on which I installed the
clamav-daemon, and am concerned that there has been a bit of
liberty-taking by pro-systemd 'agendaware'.

I issued $locate systemd 
and got 200 lines of output, including 
/etc/systemd/system/* (23 files) 
/lib/systemd/system/* (60 files)
/lib/x86_64-linux-gnu/libsystemd.so.0 (and 0.17.0)
/usr/lib/systemd (25 files)
/usr/bin/deb-systemd-helper ((and deb-systemd-invoke)
/var/lib/systemd/deb-systemd-helper-enabled/* (68 files)
/var/lib/dpkg/info/libsystemd):amd64* (5 files)

This seems a lot to me.  Please could you confirm that an ascii
installation should contain 200 systemd files as part of a normal
ascii installation.  Sorry to trouble you if these are trivial
questions, but they feel far from that.
Many thanks
Dng mailing list

Reply via email to