This one time, at band camp, Aaron M. Ucko said:
> Although I do not have clamav-daemon installed, clamav-base's postinst
> has given me an /etc/logrotate.d/clamav-daemon file containing the
> lines
> 
>      postrotate
>      /etc/init.d/clamav-daemon reload > /dev/null
>      endscript
> 
> which leads to mail from cron:
> 
> /etc/cron.daily/logrotate:
> /tmp/user/0/logrotate.Bhp8XA: line 4: /etc/init.d/clamav-daemon: No such file 
> or directory
> error: error running postrotate script
> run-parts: /etc/cron.daily/logrotate exited with return code 1
> 
>   clamav-base/LogFile: /var/log/clamav/clamav.log

This line is why - the postinst checks that the logfile line isn't null,
and if so, sets up a logrotate script for it.

In your particular case, this can easily be fixed by running
dpkg-reconfigure clamav-base, choosing yes to 'log to syslog' and entering
a null logfile line when it asks you what file to log to.  I see now
that the postinst won't disable an old logrotate file if you have moved
away from it, and that is a bug.  I will fix that in the next upload.

Unfortunately, the debconf setup is geared towards a default install,
including clamav-daemon.  The problem is that two daemons share the config
file, the milter and clamd, so I had to move the config file into base,
now that the milter no longer needs the daemon to run.  I am not sure
how to make it work much better than this, so if you have any
suggestions, please let me know.

Thanks for reporting,
-- 
 -----------------------------------------------------------------
|   ,''`.                                            Stephen Gran |
|  : :' :                                        [EMAIL PROTECTED] |
|  `. `'                        Debian user, admin, and developer |
|    `-                                     http://www.debian.org |
 -----------------------------------------------------------------

Attachment: pgpQJkMUayGri.pgp
Description: PGP signature

Reply via email to