This one time, at band camp, Clint Adams said: > > Log output, for a start. Then I would suggest running clamd for a while > > the various debugging options (LogClean LogVerbose, etc) turned on, to > > see if you can capture anyhting useful. finally of course, running an > > unstripped copy under gdb if nothing else works. > > LogVerbose and LogClean on; it choked at the end of this. > > Wed Aug 10 11:43:39 2005 -> OLE2 support enabled. > Wed Aug 10 11:43:39 2005 -> HTML support enabled. > Wed Aug 10 11:43:39 2005 -> Self checking every 3600 seconds. > Wed Aug 10 11:44:11 2005 -> /var/spool/clamav-filter/clfi.UlhnPW: OK > Wed Aug 10 11:44:12 2005 -> /var/spool/clamav-filter/clfi.K1z3tb: OK > Wed Aug 10 11:44:12 2005 -> /var/spool/clamav-filter/clfi.nZIQzx: OK > Wed Aug 10 11:44:12 2005 -> /var/spool/clamav-filter/clfi.g5AP15: OK > Wed Aug 10 11:44:13 2005 -> /var/spool/clamav-filter/clfi.24nzly: OK > Wed Aug 10 11:44:14 2005 -> /var/spool/clamav-filter/clfi.mYuxGj: OK > Wed Aug 10 11:44:14 2005 -> /var/spool/clamav-filter/clfi.ie2UVU: OK
OK, so the standard log options are not much help, I see :( some background information would be helpful: I see you're running it on a sparc of some sort, can you supply information about the environment clam is running in (RAM/CPU, etc)? Can I see the config file for clamd? How are you calling clamd? I see all the files are in /var/spool/clamav-filter - this suggests an app I am unfamiliar with placing files there and then calling clamd. Thanks, -- ----------------------------------------------------------------- | ,''`. Stephen Gran | | : :' : [EMAIL PROTECTED] | | `. `' Debian user, admin, and developer | | `- http://www.debian.org | -----------------------------------------------------------------
signature.asc
Description: Digital signature
