Clamd and systemd

[Arthur Dent]

>
> On 9/19/2012 5:54 PM, Arthur Dent wrote:
>> On Wed, 2012-09-19 at 17:00 -0400, Bill Shirley wrote:
>>> On 9/19/2012 3:36 PM, Arthur Dent wrote:
>>>
>>>> On Wed, 2012-09-19 at 10:47 +0100, Arthur Dent wrote:
>>>>

>> [snip] useful recipe (similar to mine). The thing is, for me "clamdscan
>> --no-summary --stdout" won't work. I need to tell it explicitly where
>> the config file is. I have this in my script:
>> CLAMSCAN="/bin/clamdscan -c/etc/clamd.d/scan.conf"
>> CLAMSCANOPT="--no-summary --stdout"
>>
>> and call it with ${CLAMSCAN} ${CLAMSCANOPT} - < ${MSGTMP}
>>
>> The same thing happens on the command line:
>> # clamdscan -V
>> ERROR: Can't parse clamd configuration file /etc/clamd.conf
>> # clamdscan -c /etc/clamd.d/scan.conf -V
>> ClamAV 0.97.5/15376/Wed Sep 19 19:35:38 2012
>>
>> Any ideas?
>>

> Yes, I would just symlink it.
> ln -s /etc/clamd.d/scan.conf /etc/clamd.conf
>

That sound you can hear?
It's my head thumping on the table! Doh! Why didn't I think of that?
Especially as I used exactly the same technique to solve a similar problem
a couple of months ago...

Thanks for jogging my memory. It will work of course, but it still feels a
bit of a kludge. Zdenek Pytela has pointed out that it does indeed seem to
be hardcoded so I think I might report it as a bug.

Thank you once again. I think I am all sorted now!

Cheers!

Mark