Clamav 0.95

[Rick Cooper]

> -----Original Message-----
> From: mailscanner-bounces at lists.mailscanner.info 
> [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf 
> Of Denis Beauchemin
> Sent: Wednesday, April 01, 2009 9:51 AM
> To: MailScanner discussion
> Subject: Re: Clamav 0.95
> 
> Randal, Phil a écrit :
> > Over on the clamav-users mailing list, Edwin Török says:
> >
> > "Make sure there is a symlink 
> /usr/lib64/libclamunrar_iface.so -> 
> /usr/lib64/libclamunrar_iface.so.6, run ldconfig again if necessary."
> >
> > It'll be a while before I can test this.
> >
> > Cheers,
> >
> > Phil 
> >
> >   
> 
> Phil,
> 
> I tested it on a 32 bit system and it worked. Before the 
> symlink I got:
> service clamd restart
> Stopping Clam AntiVirus Daemon:                            [FAILED]
> Starting Clam AntiVirus Daemon: LibClamAV Warning: Cannot 
> dlopen: file 
> not found - unrar support unavailable
>                                                            [  OK  ]
> 
> I then did:
> cd /usr/lib
> ln -s libclamunrar_iface.so.6 libclamunrar_iface.so
> service clamd restart
> Stopping Clam AntiVirus Daemon:                            [  OK  ]
> Starting Clam AntiVirus Daemon:                            [  OK  ]
> 
> Thanks!
> 
> Denis
> 

For some reason (don't remember why) for several versions now, the build
scripts for clamav don't run ldconfig properly after install. I have added a
call to ldconfig after install and before restarting to address this on my
systems (in my own build script). I believe the original post (on the clamav
list) concerning the check for the symlink was to check for the link and if
it was missing run ldconfig manually and check again to ensure ldconfig
created the proper link. You should *not* have to create that link by hand.

Rick


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.