|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| ARCHIVES - Tips, Tricks & Tweaks Tips and Solutions for SUSE Linux
(Please do not post questions here) |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
I will try to describe how I manage to get the final version (0.93-0.2) of ClamAV running AT LAST today, after living a whole nightmare, to finally get it up and running.
Well at least until the official package has been released, for OS 10.3. Ok, here I go... 1) The first step is to uninstall any previous version you have installed. Apparently YaST2 (if you installed ClamAV v0.92 from there) leaves traces behind, so this will not be enough. There are some serious library issues around yet with the new version, if you dont believe me, just check the ClamAV Forums to check how many people using different distros, are complaining about the lots of problem they are having to making to work ClamAV v0.93-0.2, even when there is is available a RPM for their specific distro. 2) I had to install from SOURCE the earlier version (0.92.1) to uninstall it latter. And only by doing this I really erased all the traces behind, to prepare the system to a fresh installation. So just make the traditional install process when installing from sources. Once the source package has been uncompressed:
i386 or x64 ... depending on your architecture. 3) Now you can finally proceed to install the RPM package, as usual Code:
rpm -ivlh <package-name> 5) Now try to update the virus database by running: Code:
freshclam Quote:
PD: If someone knows how to solve the WARNING issue shown in step 5), please let me know, how to bypass/solve this problem. |
|
|||
|
Yes everybody have to fight a little to make clamav to work The clamav page tell you before update how to remove the old version.
What you asked the point 5 is the key of succes,without you have nothing. If you start freshclam and succesfuly downloaded the updates you must start clamd you must edit in etc/clamd.conf keep attention of selecting local socket or tcp type setup because if booth enabled the clamd not start and also make all the required modification(tip the tcp is faster but keep in the loop zone 127.0.0.0) next easy from yast->system-> system services(run level)-> clamd enable If you have bad choices in clamd.conf clamd refuse start also if you not change the ownership of clamd directories/files from vscan to clamav if you use group clamav and user clamav and you don't have vscan user also you have an error After clamd start working you can tell you have some protection take a look at clamd.log or whatever you have in clamd.conf Also take a look to clamav unofficial pishing and scam signatures work great for me http://www.sanesecurity.com/clamav/usage.htm you can use direct download or the script's i try both method and it's ok good luck sory for my poor english bye
|
|
|||
|
hi, i'm still using suse 10.2, but i had that exact same error -
WARNING: Clamd was NOT notified: Can't connect to clamd through /var/lib/clamav/clamd-socket connect(): No such file or directory i've just been playing around with the clam setup and now i don't get that error, i've no idea what fixed the error, but these are the things i changed - 1, i ran this - $ ll /var/log/freshclam.log -rwxr-xr-x 1 root root 0 2007-01-30 15:19 /var/log/freshclam.log i changed the owner to vscan, i ran this - sudo chown vscan:vscan /var/log/freshclam.log 2, i enabled the proxy ports in /etc/freshclam.conf, i've got privoxy running so i enabled this - HTTPProxyServer 127.0.0.1 HTTPProxyPort 8118 3, i enabled this line in freshclam.conf (i changed XY to UK, that's where i am!) DatabaseMirror db.XY.clamav.net 4, i looked through freshclam.conf and clamd.conf and made sure they both had this line enabled - DatabaseDirectory /var/lib/clamav 5, i enabled this line too in clamd.conf FixStaleSocket yes that's all i did and the error has gone now! i haven't restarted everything to see if it all still works though, i want to do it as a reboot just to make sure it all works rather then restarting things manually. EDIT there's also the clamd server that can be started at boot, maybe that will get rid of the error. i only have freshclam starting at boot though. |
|
|||
|
i've seen a few places that say to comment out these two lines -
# TCPSocket 331 # TCPAddr 127.0.0.1 and enable this one in clamd.conf - LocalSocket /var/lib/clamav/clamd-socket like i think kalman is saying too, is that correct? i'm just using a standalone PC, i mean i don't have some fancy AV setup. it mentions it here - http://wiki.linux-club.de/opensuse/Vscan http://www.linux-magazin.de/heft_abo/ausga...a_abc_im_freien http://www.novell.com/coolsolutions/tip/17479.html |
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|