<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16441" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff
size=2></FONT> </DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<BLOCKQUOTE cite=mid:039201c7a772$83fe2610$0301a8c0@SAHOMELT type="cite"><PRE wrap=""><BR><SPAN class=484253913-05062007><FONT face=Arial color=#0000ff size=2>[Rick Cooper] </FONT></SPAN></PRE><PRE wrap=""><SPAN class=484253913-05062007> </SPAN>It would be possible to add an option to restart the daemon if a problem was</PRE>
encountered however I leave that up to Julian as it would require runningthe
hosts init script and I don't know if that is something he would want todo.
However if clamd has a problem your logs will note this and you could
certainly set up a script to run in cron to look for MailScanner clamderrors
and notify you. I personally monitor all my important daemons fortrouble and
I have a script that PINGS clamd that runs from cron. I reallyhaven't had
problems with clamd for at least a year and I never restart it.I only have
redhat/centos/fedora based distros though. </BLOCKQUOTE>I'm not getting into
the market for writing clamd monitoring scripts, I believe there are already
some out there.<BR>If you want to rely on clamd, it's up to you to ensure it's
running reliably.<BR><BR><PRE class=moz-signature cols="72"><BR><SPAN class=484253913-05062007><FONT face=Arial color=#0000ff size=2>[Rick Cooper] </FONT></SPAN></PRE><PRE class=moz-signature cols="72"><SPAN class=484253913-05062007><FONT face=Arial color=#0000ff size=2>I agree completely. I think MailScanner calling external init scripts would be bad given it's not generally running as root so one would have to give the MailScanner </FONT></SPAN></PRE><PRE class=moz-signature cols="72"><SPAN class=484253913-05062007><FONT face=Arial color=#0000ff size=2>user access to the script and I just don't know about how I would like that from a security standpoint. I think any responsible SysOp should be monitoring all the </FONT></SPAN></PRE><PRE class=moz-signature cols="72"><SPAN class=484253913-05062007><FONT face=Arial color=#0000ff size=2>important daemons with the ability to restart and notify in case of issues, including MailScanner. Besides even if you use clamscan, clamdscan or ClamAVModule if </FONT></SPAN></PRE><PRE class=moz-signature cols="72"><SPAN class=484253913-05062007><FONT face=Arial color=#0000ff size=2>sig database get's hosed you are going to have a problem and you need to be watching the logs for issues anyway.</FONT></SPAN></PRE><PRE class=moz-signature cols="72"><SPAN class=484253913-05062007></SPAN> </PRE><PRE class=moz-signature cols="72"><SPAN class=484253913-05062007><FONT face=Arial color=#0000ff size=2>Rick</FONT> </SPAN></PRE></BLOCKQUOTE></BODY><br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</HTML>