On 12 Mar 2010 at 8:23, jeff donovan wrote:
> I ran into a similar problem. It turned out to be AutoWhitelist
> growing eating up Hardrive space, eventually the OS had no room for
> virtual memory.
>
> see;
> /var/clamav/.spamassassin/autowhitelist
Thanks for the reply, but no spamassassin
On Mar 12, 2010, at 8:06 AM, Paul Whelan wrote:
On 11 Mar 2010 at 11:09, Jim Preston wrote:
On Mar 11, 2010, at 10:49 AM, Paul Whelan wrote:
On 11 Mar 2010 at 14:32, Matus UHLAR - fantomas wrote:
On 11.03.10 11:24, Paul Whelan wrote:
I'm getting occasional OOM faults apparently origina
On 11 Mar 2010 at 11:09, Jim Preston wrote:
> On Mar 11, 2010, at 10:49 AM, Paul Whelan wrote:
>
> >
> > On 11 Mar 2010 at 14:32, Matus UHLAR - fantomas wrote:
> >
> >> On 11.03.10 11:24, Paul Whelan wrote:
> >>> I'm getting occasional OOM faults apparently originating from
> >>> clamd on
> >>
On Mar 11, 2010, at 10:49 AM, Paul Whelan wrote:
On 11 Mar 2010 at 14:32, Matus UHLAR - fantomas wrote:
On 11.03.10 11:24, Paul Whelan wrote:
I'm getting occasional OOM faults apparently originating from
clamd on
debian.
OOM means out of memory. Either you are low on real/virtual memory,
On 11 Mar 2010 at 14:32, Matus UHLAR - fantomas wrote:
> On 11.03.10 11:24, Paul Whelan wrote:
> > I'm getting occasional OOM faults apparently originating from clamd on
> > debian.
>
> OOM means out of memory. Either you are low on real/virtual memory, or you
> have memory leak somewhere. Check
On 11.03.10 11:24, Paul Whelan wrote:
> I'm getting occasional OOM faults apparently originating from clamd on
> debian.
OOM means out of memory. Either you are low on real/virtual memory, or you
have memory leak somewhere. Check your memory status over time.
--
Matus UHLAR - fantomas, uh...@fan
I'm getting occasional OOM faults apparently originating from clamd on debian.
Is there a simple way to track down why these are happening and preventing them?
Top never shows any problems, and the machine is very lightly loaded.
Message log begins:
> Mar 3 21:18:27 rose kernel: clamd invoked
I run my mail server on 64 bit debian, running under vmware, with 512MB memory
allocated. I run clamav 0.91.1, compiled using ./configure --enable-milter
--disable-clamuko, as a milter from sendmail 8.14.1. I also use the mailwasher
server milter.
I have started to get the following in my logs,
On Mon, 23 Jan 2006 at 12:25:29 -0800, Todd Lyons wrote:
[...]
> OT:
> [...]
> Do you find that bl causes a large reduction in spam? Speaking from a
> biased point of view (because I'm getting blocked :-) that blacklist is
> not a very good one. Here's where we go for definitive info and we
> ign
On 1/23/06 12:25 PM, "Todd Lyons" <[EMAIL PROTECTED]> wrote:
> Originally the datacenter was Exodus, then it was bought by Cable &
> Wireless, then it was bought by Savvis.
I've been around email long enough that "Exodus" sends cold shivers up and
down my spine. Oh, wait...maybe that's due to th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Jan 23, 2006 at 02:12:44PM +, Nigel Horne wrote:
>>Dec 7 11:54:46 lionhead sendmail[13045]: jB7Askgv013045: SYSERR(root):
>>out of memory: Cannot allocate memory
>>ClamAv is configured in sendmail.mc as:
>>INPUT_MAIL_FILTER(`clamav', `S=l
David Weilers wrote:
Has anyone any idea about fixing the problem mentioned below?
Our sendmail complains:
Dec 7 11:54:46 lionhead sendmail[13045]: jB7Askgv013045: SYSERR(root):
out of memory: Cannot allocate memory
ClamAv is configured in sendmail.mc as:
INPUT_MAIL_FILTER(`clamav', `S=local:/
Has anyone any idea about fixing the problem mentioned below?
Our sendmail complains:
Dec 7 11:54:46 lionhead sendmail[13045]: jB7Askgv013045: SYSERR(root):
out of memory: Cannot allocate memory
ClamAv is configured in sendmail.mc as:
INPUT_MAIL_FILTER(`clamav', `S=local:/var/run/clamav/clamd.s
13 matches
Mail list logo
