On Monday 02 May 2005 23:08, Pete 'Wolfy' Hanson wrote: > Upgrading didn't seem to help me, though maybe it slowed down the > crash rate - I just had another crash about an hour ago. I'm getting > slammed at postmaster each time it crashes. This was in the logs from > the latest crash: > > May 2 14:22:24 smtp clamav-milter[153]: ClamAv: setsockopt() failed > (Invalid argument) > > Nothing leading up to it and nothing immediately after it out of the > ordinary, other than a 5 minute break before the crash where nothing > got logged (mildly unusual, but not completely unprecedented).
If that message appears, clamav-milter will fail to start, so it's not surprising nothing was logged... Review if you need the "-B" flag, and if not then don't use it. If you do use the -B flag and this message appears, then check the NIC you are telling it to use is correct. -Nigel -- Nigel Horne. Arranger, Composer, Typesetter. NJH Music, Barnsley, UK. ICQ#20252325 [EMAIL PROTECTED] http://www.bandsman.co.uk _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
