.
Also I've gone back to CentOS' native .service files for clamd and
clamav-milter. All is working well AFAICT.
unix:socket is just snakebit, and haunted...
> Original Message
> Subject: Re: [clamav-users] clamav-milter Can't Find Clamd
> Local Time: November 8, 2017 3:38
of the mailsystem get started
too soon
Original Message
Subject: 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
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 08.11.2017 um 00:06 schrieb Colony.three:
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 restarted
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 restarted again and again because it's
>>
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 restarted again and again because it's
failing, most
> 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 |grep clamd
>>
>> root 1963 93.0 25.5
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 |grep clamd
> root 1963 93.0 25.5 345992
> 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
Hi,
Have you checked the directory permissions:
ls -ld /var/run/clamd.scan /run/clamd.scan
Regards
Mark.
On 07/11/17 19:15, Colony.three wrote:
Trying to make milter see the clam daemon but can't figure out what's wrong.
CentOS7.
In /etc/clamd.d/clamd.conf:
LocalSocket
> 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
Am 07.11.2017 um 00:19 schrieb Colony.three:
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
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
17 matches
Mail list logo
