was blank, now Clam autoupdate, add f-prot

[Julian Field]

At 14:35 30/08/2003, you wrote:
>On Saturday 30 August 2003 2:17 pm, Carlo Malfatti wrote:
>
> > in my system freshclam is installed under /usr/bin, while
> > clamav-autoupdate is looking for it under /usr/local/bin.
> > Even if the hourly cronjob was stating "updating" nothing was done as
> > the updater cannot be found.
> > To solve this I created a link with:
> > ln -s /usr/bin/freshclam /usr/local/bin/freshclam
> > and now it is really updating clamav.
> > Is this sufficient or is it better to directly modify the
> > clamav-autoupdate script?
>
>I'd recommend moving freshclam from /usr/bin to its standard location of
>/usr/local/bin - that's where a normal ClamAV install puts it, and that's
>where MailScanner expects to find it.
>
>Leave it as a link if you also want it in /usr/bin for some reason, but don't
>change the autoupdate script to point to a non-standard location unless you
>have a good reason to do so.

I am just about to replace all the -autoupdate and -wrapper scripts with
new versions, so please don't change those scripts unless you *really* need to.

 From tomorrow onwards, all the virus scanner installation paths will be
specified in virus.scanners.conf and not in the scripts themselves. This
means that the command line to the scripts has had to change, so you *must*
put in place all the new -wrapper and -autoupdate scripts that will come
with the new release.

--
Julian Field
www.MailScanner.info
Professional Support Services at www.MailScanner.biz
MailScanner thanks transtec Computers for their support