:: Re: [DNG] systemd files
Top Page
Delete this message
Reply to this message
Author: Steve Litt
Date:  
To: dng
Subject: Re: [DNG] systemd files
On Fri, 2 Mar 2018 10:26:39 +0000
KatolaZ <katolaz@???> wrote:

> 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.


"Agendaware" is the best neologism I've heard in the past 2 years. It
tells it like it is.

SteveT