[users] Failing in updating to clamav and clamav-db

Michael Mansour mic at npgx.com.au
Mon Dec 24 01:02:22 CET 2007


Hi Dag,

> On Sat, 22 Dec 2007, Michael Mansour wrote:
> 
> > > Michael Mansour wrote:
> > >
> > > > I'm trying to update to the latest clamav and clamav-db and keep
getting the
> > > > following dependency problem:
> > > >
> > > > # yum --enablerepo=dag -y update clamav clamav-db
> > > > Loading "kernel-module" plugin
> > > > Setting up Update Process
> > > > Setting up repositories
> > > > dag                       100% |=========================|  951 B    00:00
> > > > sl-errata                 100% |=========================|  951 B    00:00
> > > > sl-base                   100% |=========================|  951 B    00:00
> > > > Reading repository metadata in from local files
> > > > primary.xml.gz            100% |=========================| 2.7 MB    00:00
> > > > dag       : ################################################## 8097/8097
> > > > Added 8097 new packages, deleted 0 old in 114.50 seconds
> > > > primary.xml.gz            100% |=========================| 227 kB    00:00
> > > > sl-errata : ################################################## 641/641
> > > > Added 641 new packages, deleted 0 old in 9.43 seconds
> > > > primary.xml.gz            100% |=========================| 665 kB    00:00
> > > > sl-base   : ################################################## 1750/1750
> > > > Added 1750 new packages, deleted 0 old in 24.39 seconds
> > > > Resolving Dependencies
> > > > --> Populating transaction set with selected packages. Please wait.
> > > > ---> Downloading header for clamav-db to pack into transaction set.
> > > > clamav-db-0.92-1.el4.rf.i 100% |=========================| 3.3 kB    00:00
> > > > ---> Package clamav-db.i386 0:0.92-1.el4.rf set to be updated
> > > > ---> Downloading header for clamav to pack into transaction set.
> > > > clamav-0.92-1.el4.rf.i386 100% |=========================| 8.0 kB    00:00
> > > > ---> Package clamav.i386 0:0.92-1.el4.rf set to be updated
> > > > --> Running transaction check
> > > > --> Processing Dependency: libclamav.so.2 for package: perl-Mail-ClamAV
> > > > --> Finished Dependency Resolution
> > > > Error: Missing Dependency: libclamav.so.2 is needed by package
> > perl-Mail-ClamAV
> > > >
> > > > The libclamav.so.2 is contained in clamav-0.91.2-1.el4.rf, yet it
seems that
> > > > this file isn't in clamav-0.92 ?
> > > >
> > > > Michael.
> > >
> > > clamav provides libclamav.so.3 now, so I suspect the perl-Mail-
> > > ClamAV needs to be rebuilt?
> > >
> > > You could uninstall that perl module if you don't need it though.
> >
> > I do need it though, as I use MailScanner with clamavmodule scanning support.
> >
> > Using clamavmodule with MailScanner means that scanning is faster and much
> > lower memory usage, since clamavmodule can load virus defs once into memory
> > and won't need to reload until virus def updates are made.
> >
> > Not using clamavmodule means loading virus defs each time clamscan is run and
> > without hundreds of thousands of messages per day, it's just not feasible to
> > do that.
> 
> Even though you are correct to some point, caching will cause the virus
> definitions to be kept in memory an even though clamscan invocations 
> have a little footprint on performance, loading the virus 
> definitions does not have a real impact.

I think that's "in theory", in practice using clamscan directly kills the
performance of the machine.

I remember when the 0.9x series of clamav was released (clamav 0.8x didn't
have this problem), hundreds of admins worldwide complained why their mail
servers would bog down to the point of a crawl (you can find many examples of
these issues doing a web search) and I remember I was one of them querying why
this was so, in the MailScanner mailing lists.

It turned out only two options would resolve this, using clamd or
clamavmodule. I chose the latter as it was easier to implement for me.

> (Unless you have a memory-shortage problem, but then one can ask why 
> you would be scanning emails for virusses on this system)
> 
> The obvious solution is using clamd and clamdscan.

Yes. I'll wait for the patched Mail::ClamAV though as I still prefer this way
than clamd (primarily because I don't like changing production servers with an
"untested in my setup" solution, especially over the Christmas break).

Thanks and Merry Christmas!

Michael.

> -- 
> --   dag wieers,  dag at wieers.com,  http://dag.wieers.com/   --
> [Any errors in spelling, tact or fact are transmission errors]
------- End of Original Message -------



More information about the users mailing list