On 7/23/07, Lystopad Oleksandr <[EMAIL PROTECTED]> wrote: > > But there no any debug messages in the logs.
It doesn't write to any logs, it outputs to stdout, so you'll need to run it in the foreground to see anything. > > > > And first server, where I make ``Debug no'' in config about 3 hours > > > no problem at all! Business time with high mail activity and no problems > > > with > > > clamd! I'll continue follow the clamd. > > > > > > > Ok. But why was debugging turned on in the first place? Some sample > > config you found somewhere? > > No! I like to see maximum in logs! ;) Are you absolutely sure ? :) Scanning a random file outputs 500+ lines of debug messages. You'll get bored of messages like LibClamAV debug: Signature offset: 494876, expected: 901121 (Trojan.Small-3114) repeated hundreds of times. > > Anyway, thank you very much! But Debug option requre additional tests > on FreeBSD... Not a FreeBSD specific issue. I don't think an option named 'Debug' was ever meant to be used for anything else but for tracking down problems. For sure it is not meant to be used in production environments. --Edwin _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
