-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 22 Sep 2003 6:47 am, Tommi Rintala wrote:
> Yes, the clamd is running, but something like this:
>
>
> clamav 11691 11689 0 Sep17 ?00:00:00 [clamd ]
In that case it isn't running (that's what the defunct means). It's died. Please u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday 20 Sep 2003 10:21 am, Tommi Rintala wrote:
> if, instead it is started with:
>
> /usr/local/sbin/clamd >/dev/null 2>&1
> /usr/local/sbin/clamav-milter -lo local:/var/run/clmilter.sock >/dev/null
> 2>&1
Good suggestion and may be it sh
Yes, the clamd is running, but something like this:
clamav 11691 11689 0 Sep17 ?00:00:00 [clamd ]
--
Tommi Rintalapuhelin: 044-767 7770
WasaLab Oy web: http://www.wasalab.fi/
PL 365 käyntios: Wolffintie 36 F2
65101 VAASA 65200 VA
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 li
Actually after some more investigation, I found out that clamd seems to
hang (at least in some Linux installations), if in startup the stderr and
stdout streams stop existing, which happens if it is started like this:
/usr/local/sbin/clamd
/usr/local/sbin/clamav-milter -lo local:/var/run/clmi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 19 Sep 2003 6:41 am, Tommi Rintala wrote:
> There is one entry like this (mail.log):
>
> Sep 18 04:17:10 mega clamav-milter[14321]: Expected port information from
> clamd, got 'Session(1): Time out ERROR '
> Sep 18 04:17:10 mega sm-mta[14312
Hi!
I have a problem that several (hundred) clamav-milter -processes keep on
running. They just seem to be left without data. This of course happened
overnight. Is this an issue which is (propably) allready known? I have
been following this list, but haven't seen anybody other have problem
like
