Just a quick question. When changing to 0.80, did you have to change what you used in /etc/rc.conf to start clam? Meaning, anything different or more than clamav_clamd_enable="YES" clamav_freshclam_enable="YES"
? On Wed, 10 Nov 2004 09:20:52 -0500 (EST), gfb <[EMAIL PROTECTED]> wrote: > >Date: Tue, 9 Nov 2004 22:47:01 -0500 (EST) > >From: gfb <[EMAIL PROTECTED]> > >Subject: [Clamav-users] Return value "72" from clamd <-> mimedefang.pl > > [help?] > >To: [EMAIL PROTECTED] > >Message-ID: <[EMAIL PROTECTED]> > > > >Tue Nov 9 22:03:30 EST 2004 > > > >Hello, > > > >I am looking for some assistance in tracking down a failure of clamd > >after an upgrade to ClamAV 0.80/582/. Interactively, clamscan and clamd > >appear to function normally and correctly but when called from > >MIMEDefang-filter > >(mimedefang.pl) , clamd returns an error code (72) that I have been unable > >to find > > Follow up to myself, and thanks to all of those who would have helped had my > nights sleep not clarified things. Answer: > > a. Add lots of debug yourself , but watch out for Heisenberg. :) > > b. Make sure that either the user that clamd runs as (clamav) has write > permission > on the files/directories he has to scan AND/OR > > c. Make sure that if you change the user clamd runs as (mailnull for instance) > to get scanning permission on MIMEDefang directories , that THAT user can > write > to the UNIX socket that clamd is listening on. > > d. NEVER *completely* trust automatic upgrade scripts (FreeBSD Portupgrade) > and > > e. If its almost quitting time, back away from the mail server slowly. When > the > nice Clamav guys say UPGRADE NOW they don't necessarily mean Right This > Minute. :) > > -Guy Boyd > VTA Technologies / VTA INC. > Atlanta Georgia USA > > _______________________________________________ > http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users > _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
