On Thu, Oct 14, 2010 at 4:09 PM, Luca Gibelli <l...@clamav.net> wrote: >> Since I have never seen the clamd daemon crash on any of my servers, I'm >> not particularly interested in having a program waste resources checking >> on it every 30 seconds. > > It won't take up a lot of resources. It just periodically sends a signal > to clamd. > >> Besides, why not use daemontools or one of the other existing process >> monitoring programs? Why do we need a custom one for clam? > > Well the main reason is to allow the average user to just > type: > > safe_clamd > > instead of: > > clamd > > and get the benefits of a monitoring script without any effort.
I haven't looked at the script yet, but for something simple like checking if clamd is responding, wouldn't a cronjob make more sense? Or is 1-minute granularity too coarse? -- Freddie Cash fjwc...@gmail.com _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
