On Fri, Mar 02, 2018 at 10:04:23AM +0000, leloft wrote: > 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 > https://lists.dyne.org/lurker/message/20180221.210210.37932ca6.en.html > 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 > weekly > compress > delaycompress > missingok > create 640 clamav adm > postrotate > 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 > fi > endscript > } > > 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'.
Hi, It's probably just that the upstream package maintainer has made the assumption that Debian should only run systemd, and nothing else ever. You might call it pro-systemd 'agendaware', if you like. It just seems to have become a shared habit of many (but not all) maintainers. That's why we are here, after all... > > 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 > leloft Most of those "alarming" files are just systemd units files, put there by daemons/packages/utilities who "also" support systemd in a way or another. So they are not alarming but just *totally* *harmless* if you don't have a running systemd as PID 1, since only systemd understands and can run them. It would be *totally* *useless* (and utterly *stupid* IMHO) to fork, rebuild, and maintain a few more hundred packages only because they happen to provide a systemd unit file for those systems where systemd is used. libsystemd0 is used by some daemons to verify if systemd is running or not. If it's not, libsystemd is *totally* *harmless*. HND KatolaZ P.S.: I guess we should consider including the last two paragraphs above on www.devuan.org, or put it in the mailing list signature... -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ]
signature.asc
Description: Digital signature
_______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
