Date: Thu, 11 Mar 2004 08:30:52 -0500 From: Bart Silverstrim <bsilver@chrononomicon.com> To: FreeBSD Questions Mailing List <freebsd-questions@freebsd.org> Subject: Re: clamav ports Message-ID: <51130C98-7360-11D8-95AC-000A956D2452@chrononomicon.com> In-Reply-To: <20040311000001.7049fc62@earth.upton.net> References: <65388515-7301-11D8-8730-000A956D2452@chrononomicon.com> <404FCE46.3010902@theatre.msu.edu> <A7F1FFDC-7304-11D8-8730-000A956D2452@chrononomicon.com> <20040311000001.7049fc62@earth.upton.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 11, 2004, at 12:00 AM, Paul Murphy wrote: > Just a thought, do you have '#NotifyClamd > [/optional/config/file/path]' > uncommented in freshclam.conf > I didn't, but I did uncomment it now. I don't have a freshclam running from the rc.conf; I have a crontab file for root that is 0 */4 * * * /usr/local/bin/freshclam Should I be running the script file instead from rc.conf? Do both ways still notify clamd?...I don't know what config file it should be pointing to, but since it was "optional" I didn't add one (just have a line in freshclam.conf stating "NotifyClamd"). I still have no idea why the system just started magically picking up the virus that after the rebuild it was letting through. Maybe it happened after it did a database consistency check? Thank you! -Bart
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51130C98-7360-11D8-95AC-000A956D2452>