At 11:30 yesterday, Chris Barber wrote:
One thing with the fetch-sanesecurity-sigs I have seen (on two different servers now) is that clamd ends up in a stopped state until I manually restart it. When this happens, the script returns the following error from cron: /<path>/fetch-sanesecurity-sigs: line 215: kill: (29429) - No such process
Interesting; could you check syslog for any relevant messages from clamd at that time?
Thanks, -- Malcolm Scott Retrosnub Internet Services http://www.retrosnub.co.uk/