[Pkg-clamav-devel] Initial start of clamav-daemon

Dilyan Palauzov dilyan.palauzov at aegee.org
Wed Apr 27 20:12:20 UTC 2016


Hello,

if there is nothing in /var/lib/clamav this happens:

root at debian-vm:/var/lib/clamav# clamd
LibClamAV Error: cli_loaddbdir(): No supported database files found in 
/var/lib/clamav
ERROR: Can't open file or directory


and clamd 0.99 is not forked.

Anyway, there is no difference between "not starting clamd because 
ConditionPathExistsGlob said so" and "not starting clamd because 
/var/lib/clamav is emtpy", except that in the latter case using socket 
activation, freshclam can start clamd by writing to the common socket.



On 04/24/16 20:59, Scott Kitterman wrote:
> On April 24, 2016 1:59:24 PM EDT, Sebastian Andrzej Siewior <sebastian at breakpoint.cc> wrote:
>> On 2016-04-22 18:31:10 [+0200], Dilyan Palauzov wrote:
>>> Hello,
>> Hi,
>>
>>> I propose removing the ConditionPathExistsGlob from
>>> clamav-daemon.s(ervice,ocket). Then, once freshclam is ready, it will
>> notify
>>> clamd over the socket, systemd will start clamd because of
>>> clamav-daemon.socket  and everything is fine.  If somebody tries to
>> contact
>>> the socket before freshclam is ready, and clamd starts and fails due
>> to
>>> missing databases, we have the current situation: in order to start
>> clamd,
>>> it has to be restarted manually, once the databases have been
>> downloaded.
>>> So removing ConditionPathExistsGlob is an improvement, as it boots
>> the
>>> system correctly in more cases, than now.
>> This does not sound that bad. I am not sure at the time of writting but
>> I
>> *think* that we could start clamd without signatures (which is what you
>> suggests).
> I don't believe we can.  If libclamav doesn't find signatures when initialized, my recollection is that it errors out.
>
> Scott K




More information about the Pkg-clamav-devel mailing list