More information about the problem. When I run the clamd with Debug
options (and LogTime), I get this output to logfile. From the timestamps
you can see, why I think this is a problem.

Mon Sep 22 10:23:08 2003 -> +++ Started at Mon Sep 22 10:23:08 2003
Mon Sep 22 10:23:08 2003 -> Log file size limited to 1048576 bytes.
Mon Sep 22 10:23:08 2003 -> Verbose logging activated.
Mon Sep 22 10:23:08 2003 -> Running as user clamav (UID 600, GID 600)
Mon Sep 22 10:23:08 2003 -> Reading databases from
/opt/wasalab/share/clamav
Mon Sep 22 10:23:08 2003 -> Protecting against 9640 viruses.
Mon Sep 22 10:23:08 2003 -> Unix socket file /var/clamav/clamd.sock
Mon Sep 22 10:23:08 2003 -> Setting connection queue length to 15
Mon Sep 22 10:23:08 2003 -> Listening daemon: PID: 1126
Mon Sep 22 10:23:08 2003 -> Maximal number of threads: 5
Mon Sep 22 10:23:08 2003 -> Archive: Archived file size limit set to
10485760 by
tes.
Mon Sep 22 10:23:08 2003 -> Archive: Recursion level limit set to 5.
Mon Sep 22 10:23:08 2003 -> Archive: Files limit set to 1000.
Mon Sep 22 10:23:08 2003 -> Archive support enabled.
Mon Sep 22 10:23:08 2003 -> Mail files support enabled.
Mon Sep 22 10:23:08 2003 -> ThreadWatcher: Started in process 1129
Mon Sep 22 10:23:08 2003 -> Self checking every 3600 seconds.
Mon Sep 22 10:23:09 2003 -> Timeout set to 180 seconds.
Mon Sep 22 10:23:09 2003 -> SelfCheck: Database status OK.
Mon Sep 22 10:23:09 2003 -> SelfCheck: Integrity OK
Mon Sep 22 10:27:02 2003 -> Session 1 stopped due to timeout.
Mon Sep 22 10:30:05 2003 -> Session 2 stopped due to timeout.
Mon Sep 22 10:33:11 2003 -> Session 1 stopped due to timeout.
Mon Sep 22 10:36:16 2003 -> stream: Worm.Gibe.F FOUND
Mon Sep 22 10:38:09 2003 -> Session 1 stopped due to timeout.
Mon Sep 22 10:41:12 2003 -> Session 2 stopped due to timeout.
Mon Sep 22 10:44:22 2003 -> Session 1 stopped due to timeout.
Mon Sep 22 10:47:28 2003 -> Session 0 stopped due to timeout.
Mon Sep 22 10:50:48 2003 -> Session 3 stopped due to timeout.
Mon Sep 22 10:52:16 2003 -> Session 0 stopped due to timeout.

And at this stage, the clamd is not accepting connections, or scanning
mails....

Currently I have updated to sendmail-8.12.10, because of the things found
from previous sendmail. But the problem persists. I am also running
spamassassin (and have tried without), which keeps running couple weeks
without any problems.

Is there a way to get more debug output from the clamd, other than
enabling the Debug -flag in configuration file?

yours,
-- 
  Tommi Rintala    puhelin:   044-767 7770
  WasaLab Oy       web:       http://www.wasalab.fi/
  PL 365           käyntios:  Wolffintie 36 F2
  65101 VAASA                 65200 VAASA



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Clamav-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/clamav-users

Reply via email to