Joel Esler wrote:
> On Fri, Jan 26, 2018 at 04:51:26PM +0100, Per Jessen wrote:
>>Jacek Zapała wrote:
>>
>>[snip]
>>
>>
>>In case this helps anyone, we have worked around this by letting our
>>daemon check /proc/self/fd after each scan and look for "(deleted)".
>>File descriptors that match are th
On Fri, Jan 26, 2018 at 04:51:26PM +0100, Per Jessen wrote:
Jacek Zapała wrote:
[snip]
In case this helps anyone, we have worked around this by letting our
daemon check /proc/self/fd after each scan and look for "(deleted)".
File descriptors that match are then closed.
I appreciate this won't
Jacek Zapała wrote:
> Same here. clamd 0.99.2
>
> I have clamd processes running on separate servers.
> Each running clamd keeps 1024 file descriptors open (all that it
> can):
>
> # ls -l /proc/29866/fd
> total 0
> lr-x-- 1 root root 64 Jan 26 15:44 0 -> pipe:[4007352]
> l-wx-- 1 root
W dniu 2018-01-26 15:26, Per Jessen napisał(a):
Per Jessen wrote:
Dianne Skoll wrote:
Hi,
Something went badly wrong with clamd recently; it's stuck with
hundreds/thousands of open files per process and interrupting mail
flow.
When a scanning thread finishes, I see this in the strace outp
Gary R. Schmidt wrote:
> It might be useful to let us know some rather minor and truly
> insignificant things, such as what version of ClamAV you are running,
> and, perhaps, what Operating System you are running it on?
ClamAV 0.99.2, various versions of Linux including Debian Jessie x86_64
an
Per Jessen wrote:
> Dianne Skoll wrote:
>
>> Hi,
>>
>> Something went badly wrong with clamd recently; it's stuck with
>> hundreds/thousands of open files per process and interrupting mail
>> flow.
>>
>> When a scanning thread finishes, I see this in the strace output.
>> (I ran clamdscan /etc/
On 27/01/2018 00:50, Per Jessen wrote:
Dianne Skoll wrote:
Hi,
Something went badly wrong with clamd recently; it's stuck with
hundreds/thousands of open files per process and interrupting mail
flow.
When a scanning thread finishes, I see this in the strace output.
(I ran clamdscan /etc/hosts
Dianne Skoll wrote:
> Hi,
>
> Something went badly wrong with clamd recently; it's stuck with
> hundreds/thousands of open files per process and interrupting mail
> flow.
>
> When a scanning thread finishes, I see this in the strace output.
> (I ran clamdscan /etc/hosts as a test):
>
> [pid 37
On 26/01/2018 18:33, Dianne Skoll wrote:
Hi,
Something went badly wrong with clamd recently; it's stuck with
hundreds/thousands of open files per process and interrupting mail flow.
When a scanning thread finishes, I see this in the strace output.
(I ran clamdscan /etc/hosts as a test):
[pid
Hi,
Something went badly wrong with clamd recently; it's stuck with
hundreds/thousands of open files per process and interrupting mail flow.
When a scanning thread finishes, I see this in the strace output.
(I ran clamdscan /etc/hosts as a test):
[pid 3707] 02:11:01 sendto(295, "/etc/hosts: OK\
10 matches
Mail list logo
