Ricardo Kleemann wrote:
Hi,
I run clamdscan from within a script and wanted to know if
it is possible to detect any problem with clamd when running
clamdscan?
Last night clamd ran into a strange problem, I don't know
what it was, but basically it seemed to be stuck and all
instances of my script were basically "hung".
Will clamdscan hang forever if for some reason it can't
communicate with clamd?
I didn't have a chance to investigate anymore but all I
noticed is that my kernel (linux) was complaining about
threads, and things only returned to normal after I stopped
and restarted clamd. Maybe clamd was leaking threads (I'm
running 0.65)?
I don't know... but in any case, clamd has been VERY stable
for me, my main concern is to be able to determine when
there's a problem. I was surprised that clamdscan didn't
time out, but rather seemed to be hung?
Is it possible to ensure that clamdscan times out and
returns some sort of error?
Try http://mikecathey.com/code/clamdwatch/
Works great
:)
--
Please avoid sending me Microsoft Office attachments.
See http://www.newsforge.com/software/04/03/27/0134204.shtml
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Clamav-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/clamav-users
