Skip to main content

Clamav Update Problem

I use Clamav for my antivirus in all of my Slackware box (laptop and 2 desktops). On every machine, i set the update mechanism differently. For my desktops, i set it automatically update every 15 minutes and one hour because they are all connected to the Internet, so it's not a problem to use this settings, but for my laptop who doesn't connected all the time, this could be problem (I can also set it to become automatic, but it would be a waste), so i make the update process manually.

The problem arose when i tried to update my database from my campus network. When the traffic was so full, the update process failed all the time and causing Clamav to blacklist the mirror. Unfortunately, the mirror Clamav blocked was the primary server, so when i tried to update the virus database at home, it always failed. I even tried to re-install the apps, but the problem persists. The problem is already listed on the Clamav Support page, so by just doing what it's written on that page, i'm able to download the update again.

It seems that Clamav will blacklist a mirror when you have a bad network and update process failed all the time. If you are sure that your network is good, then find mirrors.dat and remove them. It's Clamav's file that store the mirror information and the status (normal or blacklisted). After you deleted them, Clamav will create a new one and use the default server to download the updates.

Popular posts from this blog

Running Rsync Via Proxy

One way to get the latest Slackware updates is by running rsync to syncronize your local repository and the main repository that hold the Slackware packages. Eric Hameleers has provided a great script called and how i modified this tool has been discussed on my previous post. In general, it works, except for one problem, when your computer is connecting to the Internet through a proxy.

My workstation at my office is connected to the Internet through a proxy, so i can't use normal rsync to work normally. I browsed the web and i found this site which tells us about how we should modify our squid configuration to allow rsync connection from any computer from our local networks. I asked my sysadmin to try this script. He agreed and he updated the squid configuration on the proxy.

Next, i need to update my environment variable RSYNC_PROXY to the host of the proxy and also the port. Let's say you are running a proxy on and port 8080, then you need to run …

NVidia Legacy Unix Driver Update

NVidia has released an updated legacy drivers to support X.Org 1.19 with ABI 23. It has been mentioned in the UNIX drivers, but you can directly find the drivers from the links below:
NVidia 304.134 (x86x86_64)NVidia 340.101 (x86, x86_64) I have tested the 304.134 driver and it's working great here. I can finally remove x from my /etc/slackpkg/blacklist file since it's a showstopper for me.
Aside from legacy driver, NVidia has also released their latest driver 375.26 (x86, x86_64), which brings support for newer cards and also many new features (including X.Org 1.19 with ABI 23 support). 

Security Update: firefox, irssi, pidgin

Three security updates were released for today:
firefox: Upgraded to 45.4.0esr for 14.1 and 14.2 and 49.0 for currentirssi: Upgraded to 0.8.20pidgin: Upgraded to 2.10.11, 2.10.12, and 2.11.0 for all stable Slackware releases depending on their support Some minor update in current:
mkinitrd: Add dmsetup supportemacs: Upgraded to 25.1qt: Fix multilib issue network-scripts: Fix minor issue