From: George Georgalis <georgalis@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: problem with linux 2.6.11 and sa
Date: Fri, 4 Mar 2005 15:58:43 -0500 [thread overview]
Message-ID: <d91f4d0c050304125843dc1397@mail.gmail.com> (raw)
In-Reply-To: <d91f4d0c050304105339eb297d@mail.gmail.com>
On Fri, 4 Mar 2005 13:53:50 -0500, George Georgalis <georgalis@gmail.com> wrote:
> On Thu, 3 Mar 2005 23:37:06 -0500, Jeff Garzik <jgarzik@pobox.com> wrote:
> > On Thu, Mar 03, 2005 at 01:57:28PM -0500, George Georgalis wrote:
> > > I recall a problem a while back with a pipe from
> > > /proc/kmsg that was sent by root to a program with a
> > > user uid. The fix was to run the logging program as
> > > root. Has that protected pipe method been extended
> > > since 2.6.8.1?
> > >
> > > 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.
> >
> > Does reverting to 2.6.10 fix this behavior?
>
> Yes, actually I revert to 2.6.8.1; will try 2.6.10 today...
I did make oldconfig (n,n,n) with my 2.6.11 .config
and seems to be working normal. Could
CONFIG_PREEMPT_BKL=y
have anything to do with it?
http://galis.org/linux-2.6.11-sta.config
http://galis.org/linux-2.6.10-sta.conf
// George
--
George Georgalis, systems architect, administrator Linux BSD IXOYE
http://galis.org/george/ cell:646-331-2027 mailto:george@galis.org
next prev parent reply other threads:[~2005-03-04 23:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050303184605.GB1061@ixeon.local>
2005-03-03 18:57 ` problem with linux 2.6.11 and sa George Georgalis
2005-03-04 4:37 ` Jeff Garzik
2005-03-04 18:53 ` George Georgalis
2005-03-04 20:58 ` George Georgalis [this message]
2005-03-03 17:34 George Georgalis
2005-03-21 22:25 ` Andrew Morton
2005-03-21 22:48 ` 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=d91f4d0c050304125843dc1397@mail.gmail.com \
--to=georgalis@gmail.com \
--cc=jgarzik@pobox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.