> Am 05.12.2017 um 08:13 schrieb Colony.three:
>
>> As Red Hat hasn't solved the problem of unix:sockets, I had to make my own
>> systemd files. But there's a little problem.
>>
>> clamd.socket
>>
>> [Unit]
>> Description=Socket for Clam AntiVir
As Red Hat hasn't solved the problem of unix:sockets, I had to make my own
systemd files. But there's a little problem.
clamd.socket
==
[Unit]
Description=Socket for Clam AntiVirus userspace daemon
Documentation=man:clamd(8)
PM
> UTC Time: November 8, 2017 11:38 PM
> From: h.rei...@thelounge.net
> To: clamav-users@lists.clamav.net
>
> Am 09.11.2017 um 00:13 schrieb Colony.three:
>
>> Yes my first posts were not close to the problem, as there was an evolution
>> in my thinking through the
Re: [clamav-users] clamav-milter Can't Find Clamd
> Local Time: November 7, 2017 4:26 PM
> UTC Time: November 8, 2017 12:26 AM
> From: h.rei...@thelounge.net
> To: clamav-users@lists.clamav.net
>
> Am 08.11.2017 um 00:06 schrieb Colony.three:
>
>> Am 07.11.2017 um 22:46 schrieb
Am 07.11.2017 um 22:46 schrieb Colony.three:
>> So much for that theory. There are about a million of these in the logfile.
>> It's not making its own socket for unknown reasons which may be New To
>> Science.
>>
>> well, that looks like clamd is restarte
> But I'm beginning to gather that the reason clamd is not creating its socket
> is that it's still loading current pattern databases. It's consuming 98% of
> CPU, although I'm not seeing any sign of network traffic, which seems odd.
> The signature database (main.cld) is 300MB and daily.cld
> On Tue, 7 Nov 2017, Colony.three wrote:
>
>> Since I installed clamd a week ago, I've had to manually create the
>> /run/clamd.scan directory and the clamd.sock file. The clamd daemon is not
>> doing this even though it is running as root.
>>
>> ps aux |
> Hi,
>
>> Have you checked the directory permissions:
>>
>> ls -ld /var/run/clamd.scan /run/clamd.scan
>>
>> Regards
>> Mark.
>
> Sure, it's the third one up from this post.
Since I installed clamd a week ago, I've had to manually create the
/run/clamd.scan directory and the clamd.sock file.
Hi,
> Have you checked the directory permissions:
>
> ls -ld /var/run/clamd.scan /run/clamd.scan
>
> Regards
> Mark.
Sure, it's the third one up from this post.
___
clamav-users mailing list
clamav-users@lists.clamav.net
> Trying to make milter see the clam daemon but can't figure out what's wrong.
> CentOS7.
>
In /etc/clamd.d/clamd.conf:
LocalSocket /var/run/clamd.scan/clamd.sock
LocalSocketGroup virusgroup
LocalSocketMode 660
FixStaleSocket yes
AllowSupplementaryGroups yes
Trying to make milter see the clam daemon but can't figure out what's wrong.
CentOS7.
>>> In /etc/clamd.d/clamd.conf:
>>> LocalSocket /var/run/clamd.scan/clamd.sock
>>> LocalSocketGroup virusgroup
>>> LocalSocketMode 660
>>> FixStaleSocket yes
>>>
>>> AllowSupplementaryGroups yes
>>>
>>> and you
Original Message
> Subject: Re: [clamav-users] clamav-milter Can't Find Clamd
> Local Time: November 6, 2017 4:01 PM
> UTC Time: November 7, 2017 12:01 AM
> From: h.rei...@thelounge.net
> To: clamav-users@lists.clamav.net
>
> Am 07.11.2017 um 00:19
Trying to make milter see the clam daemon but can't figure out what's wrong.
CentOS7.
In /etc/clamd.d/clamd.conf:
LocalSocket /var/run/clamd.scan/clamd.sock
LocalSocketGroup virusgroup
LocalSocketMode 660
FixStaleSocket yes
... at which point I found that Yum hadn't installed the socket for
13 matches
Mail list logo
