This one time, at band camp, Clint Adams said: > > Change this to "/usr/bin/clamscan --debug" > > > > Your load will go up for a while, but we'll get a chance to see what th > > eproblem is. then send me the last several logs after a crash/lockup. > > Is clamscan supposed to choke and hang then?
clamdscan is just a client that passes all requests to clamd for the actual scanning. clamscan and clamd both use the same library for scanning, so the chances are good that whatever will blow up clamd will also blow up clamscan. The difference is that clamscan is a single instance, rather than a running daemon - this means more startup overhead but also a single stupified process won't halt mail processing. So, we're using it on the assumption that something will come along and kill it, yes. But it will be slightly different, and will need a more watchful eye to see which one is dead, as most mail will continue normally. Thanks, -- ----------------------------------------------------------------- | ,''`. Stephen Gran | | : :' : [EMAIL PROTECTED] | | `. `' Debian user, admin, and developer | | `- http://www.debian.org | -----------------------------------------------------------------
signature.asc
Description: Digital signature
