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 agai
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
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 like
> 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 i
> 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 3459
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 258
> 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. Th
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
http://lists.clamav.net/cgi-bin/
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 /var/run/cl
> 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
I use exim with clamav.
Everything is working fine and mails with attachment get scanned,and if
malware is found, these are rejected. BUT I have lots of
malware acl condition: error while creating mbox spool file
eximscan 100M 100M 0 100% /var/spool/exim/scan
Why is not the
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
Ravi wrote:
Thanks Kris for your comments. Currently we scan the incoming
files(zips/archives) placed on the local hard drive with the
clamdscan(which uses clamd daemon), Can you share more info on what you
meant on handling the result differently if we are using the clamdscan?
Whatever calls c
Thanks Kris for your comments. Currently we scan the incoming
files(zips/archives) placed on the local hard drive with the
clamdscan(which uses clamd daemon), Can you share more info on what you
meant on handling the result differently if we are using the clamdscan?
Thanks
Ravi
On Tue, Nov 7, 201
Hi,
Still having a few issues here, even after ' rm -rfv mirrors.dat '
Reading CVD header (main.cvd): WARNING: main.cvd not found on remote server
WARNING: Can't read main.cvd header from db.gb.clamav.net (IP: 193.1.193.64)
WARNING: DNS record is older than 3 hours.
WARNING: Invalid DNS reply. F
15 matches
Mail list logo
