On Sun, 15 Feb 2009 10:30:22 +0200 Török Edwin <edwinto...@gmail.com> wrote:
> On 2009-02-15 07:15, Steve wrote: > > My main frustration is that the only way I can get more information from > > the applications is to rewrite the > > code itself... at least it's written in a real language (runs for cover!). > > but it would be great to be able to change the log level to get more > > detailed info out. Then I would be able to take a more proactive approach > > in debugging this problem. > > > > Enable LogVerbose in clamd.conf, currently it will show lot of debugging > messages about the protocol > (I'll change this before the RC, so it won't output debug messages, > unless you also specify Debug yes. But for now, enabling LogVerbose in > clamd.conf should give plenty of > protocol messages. At least one can see if clamd actually received a > command from the milter). > > Another thing you may try is to use 'tcp:localhost:3310' in > clamav-milter.conf, instead of the unix socket, and see if that makes > any difference. > > Best regards, > --Edwin > _______________________________________________ > Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net > http://www.clamav.net/support/ml Will do. It'll be about 12 hours or so before I try it... timezones and all that. Can I use logverbose on the milter as well?? Cheers, Steve -- Steve <st...@greengecko.co.nz> _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
