Clamav 0.95

[Scott Silva]

on 4-1-2009 8:29 AM Rick Cooper spake the following:
>  
> 
>> -----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 11:04 AM
>> To: MailScanner discussion
>> Subject: Re: Clamav 0.95
>>
>> Rick Cooper a �crit :
>>>  
>>>
>>>   
>>>> -----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.
>>>
>>>
>>>   
>> Rick,
>>
>> Just tried it on my last MS server and it didn't work (RHEL 5.3):
>> # ldconfig
>> # service clamd restart
>> Stopping Clam AntiVirus Daemon:                            [  OK  ]
>> Starting Clam AntiVirus Daemon: LibClamAV Warning: Cannot 
>> dlopen: file 
>> not found - unrar support unavailable
>>                                                            [  OK  ]
>> # ln -s /usr/lib/libclamunrar_iface.so.6 
>> /usr/lib/libclamunrar_iface.so
>> # service clamd restart
>> Stopping Clam AntiVirus Daemon:                            [  OK  ]
>> Starting Clam AntiVirus Daemon:                            [  OK  ]
>>
>> Denis
>>
> 
> IIRC one of the people having the issue with the 0.94x to 0.95 upgrade and
> not having the link built correctly  by ldconfig eventually found they had
> two copies of the lib one in /usr/lib and one in either /usr/local/lib or
> /lib and ldconfig built the link in the wrong place. Any way you look at it
> there is a problem as ldconfig should build the link against the most recent
> lib version. And I think (99.9% sure) the default location for the lib is
> /usr/local/lib. If you do an ls -lh /usr/local/lib/libclamunrar*
> /usr/lib/libclamunrar do you find only one copy/version in one place?
> 
Source installs default to /usr/local/lib, but most rpm distros use /usr/lib.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 258 bytes
Desc: OpenPGP digital signature
Url : http://lists.mailscanner.info/pipermail/mailscanner/attachments/20090401/1d666426/signature.bin