From: Andrew Morton <akpm@osdl.org>
To: george@galis.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: problem with linux 2.6.11 and sa
Date: Mon, 21 Mar 2005 14:25:55 -0800 [thread overview]
Message-ID: <20050321142555.47b1e5a1.akpm@osdl.org> (raw)
In-Reply-To: <20050303173459.GC952@ixeon.local>
"George Georgalis" <george@galis.org> wrote:
>
> I'm very defiantly seeing a problem with the 2.6.11
> kernel and my spamassassin setup. However, it's not
> clear exactly where the problem is, seems like sa
> but it might be 2.6.11 with daemontools + qmail +
> QMAIL_QUEUE.
>
> A sure sign of it is no logs (with debug) for
> remote sa connections which score "0/0" and correct
> operation with local "cat spam.txt | spamc -R"; fix
> is to use the older kernel.
>
> SA has stopped stdout logging completely with 2.6.11
> in addition to the all pass score. But the message
> seems to go through my temp queue (for testing) and
> sent on to my local MDA. I'm not sure if it's a sa
> problem with the kernel or the new kernel doing
> something new with pipes from tcp connections.
> Maybe the new kernel is not making files available
> (eg 0 bytes), until the writing pipe is closed?
> That would make my SA test a zero byte file, which
> would pass, close, become full, and the file piped
> to local MDA is full? ...humm then I'd get a score
> of "0/5"... this sounds like a SA problem with the
> new kernel, ideas?
George, did you end up getting to the bottom of this? I'd be suspecting a
bug in the new pipe code, or an application bug which was triggered by the
new pipe code.
next prev parent reply other threads:[~2005-03-21 22:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 17:34 George Georgalis
2005-03-21 22:25 ` Andrew Morton [this message]
2005-03-21 22:48 ` George Georgalis
[not found] <20050303184605.GB1061@ixeon.local>
2005-03-03 18:57 ` George Georgalis
2005-03-04 4:37 ` Jeff Garzik
2005-03-04 18:53 ` George Georgalis
2005-03-04 20:58 ` George Georgalis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050321142555.47b1e5a1.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=george@galis.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®