and where is the config file located in order to do this.
I am running behind a proxy (privoxy is the name of the proxy software)
the proxy ip is 192.168.0.2 port 8118
these are the contents of avast-update in usr/bin
#!/bin/sh
Updates avast! virus database. For use from cron table.
AVASTDIR=$HOME/.avast
VPSFILE=$AVASTDIR/400.vps
URL_UPDATE=“http://files.avast.com/files/latest/400.vps”
URL_UPDATE_MD5=“http://files.avast.com/files/latest/400vps.md5”
if test ! -d $AVASTDIR ; then
echo “You have to run avast! at least once before you can update it.” >&2
exit 1
fi
if test -f $AVASTDIR/lockfile-$USER ; then
echo “avast! is running, can’t update.” >&2
exit 1
fi
if test -f $VPSFILE ; then
md5_current=md5sum $VPSFILE | cut -c1-32
fi
file_md5=$VPSFILE.new.md5
wget -q -O $file_md5 $URL_UPDATE_MD5 && md5_update=cat $file_md5 | cut -c1-32
rm -f $file_md5
if test “x$md5_current” != “x$md5_update” ; then
wget -q -O $VPSFILE.new.$$ $URL_UPDATE && mv -f $VPSFILE.new.$$ $VPSFILE
fi
Hallo,
there are more ways how to update avast’s virus database. Esentially, all what you need is to download certain file (400.vps) from the web and invoking avastvpsreload.
There are three scripts doing this task - avastvpsupdate.pl and avastvpsupdate.sh are included of the engine package. Avast-update is a part of the workstation package.
You can use the --proxy-user and --proxy-passwd switches for wget, or You can set the environment variables http_proxy (even in the full form like this: http://user:pass@proxyurl:proxyport ) before running the script.
The avastvpsupdate.sh script is able to take proxy settings from /etc/avastvpsupdate.conf file. IMHO the best way is to have the proper environment variable filled globally for the whole system. This way, many proxy-sensitive applications can adopt the proper setting from this variable directly and there’s no need to set it again and again for each particular utility.
PC