Per Jessen wrote:
Dennis Peterson wrote:
And as an old school Unix admin who still believes in the mentoring
responsibility of my position, I will make recommendations from time
to time regarding best practices and I recommend if you run freshclam
as a daemon that you monitor it and restart it if needed.
Do you do that for ALL your daemon processes? As an old school
mainframe sysprog, I don't monitor any of my daemon processes. (apart
from *some* status-monitoring via SNMP).
Throwing my 2c in,
I have a cron job that runs every couple hours and just reports on the
status of various daemons. It tells me if any of them are missing,
basically.
But, it doesn't try to restart them (bad idea, IMO; for most daemons,
it's better for a human to go look at why the process isn't running and
try to solve it, instead of just blindly/programatically trying to
restart it). It's just warning me that something that _should_ be
running is not.
In the 2 years I've been running clamav, I haven't had freshclam come up
missing.
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html
