This one time, at band camp, Justin B Rye said:
> I'm not running the daemon, so I'm glad to see the pid-check in the
> new /etc/logrotate.d/clamav-freshclam:
> 
>  [ -f /var/run/clamav/freshclam.pid ] && kill -HUP `cat 
> /var/run/clamav/freshclam.pid` > /dev/null
> 
> However, testing for it this way, the last thing the postrotate
> script does is fail to find it, so logrotate reports it as an error:
> 
>  /etc/cron.daily/logrotate:         
>  error: error running postrotate script         
>  run-parts: /etc/cron.daily/logrotate exited with return code 1
> 
> Now, if you did it this way round (cf /etc/logrotate.d/samba) it
> would report an error only if something went wrong with the kill: 
> 
>  [ ! -f /var/run/clamav/freshclam.pid ] || kill -HUP `cat 
> /var/run/clamav/freshclam.pid` > /dev/null

Right - I saw the error of my ways already.  What I have actually done
is put a new reload_log target in the init script, and let
start-stop-daemon do the work.  This will be uploaded shortly.

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

Attachment: pgpXMrkDEOn7Z.pgp
Description: PGP signature

Reply via email to