[clamav-users] Unable to run clamd in /opt/directory

[Deyan Chepishev]

Hi,

This is probably caused by permissions of the /opt which do not allow the user 
which clamd is running as, to access this directory.

In such cases, you can try option:

clamdscan --stream

In this case, if the user executing clamdscan has permissions over the 
directory, clamdscan reads the files and streams them to clamd using the clamd 
socket.
If you do not use this option, behavior is selected automatically, which for 
scans where clamd and clamdscan are started on the same machine, is clamd to try 
to directly scan the directory, which causes troubles if his user do not have 
permissions to traverse the directory/files.


Regards,
Deyan


Dennis Peterson wrote:
> What are the directory permissions/extended permissions for /opt?
>
> Did you try sudo -u clamdUserName cat /opt/clamd.conf to see if the clamd user
> has permission to access the file?
>
> dp
>
> On 11/4/15 6:15 AM, P K wrote:
>> Hi Guys,
>>
>> I am seeing config file parse error when using config file inside /opt/
>> directory.
>>
>> Curious why unable to run clamd config in /opt directory.   In other system
>> with 0.98.6  its working fine.
>>
>> Below are output:
>>
>> sudo /usr/sbin/clamd --version -c ./clamd.conf
>> ClamAV 0.98.7
>>
>>
>> pk at pk-x:~$ ls -ltr /opt/clamd.conf
>> -rw-r--r-- 1 root root 1981 Nov  4 19:07 /opt/clamd.conf
>>
>> pk at pk-x:~$ ls -ltr ./clamd.conf
>> -rw-r--r-- 1 root root 1981 Nov  4 19:07 ./clamd.conf
>>
>> pk at pk-x:~$ sudo /usr/sbin/clamd -c /opt/clamd.conf
>> *ERROR: Can't open/parse the config file /opt/clamd.conf*
>>
>> pk at pk-x:~$ sudo /usr/sbin/clamd -c ./clamd.conf
>> Limits: Global size limit set to 104857600 bytes.
>> Limits: File size limit set to 26214400 bytes.
>> Limits: Recursion level limit set to 10.
>> _______________________________________________
>> Help us build a comprehensive ClamAV guide:
>> https://github.com/vrtadmin/clamav-faq
>>
>> http://www.clamav.net/contact.html#ml
>
> _______________________________________________
> Help us build a comprehensive ClamAV guide:
> https://github.com/vrtadmin/clamav-faq
>
> http://www.clamav.net/contact.html#ml