mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Chris Wright <chrisw@osdl.org>, Matt Mackall <mpm@selenic.com>,
	Michael Kerrisk <mtk-manpages@gmx.net>,
	mingo@elte.hu, linux-kernel@vger.kernel.org,
	michael.kerrisk@gmx.net, akpm@osdl.org
Subject: Re: Broke nice range for RLIMIT NICE
Date: Fri, 29 Jul 2005 14:07:56 -0700	[thread overview]
Message-ID: <20050729210756.GK19052@shell0.pdx.osdl.net> (raw)
In-Reply-To: <1122670930.9381.25.camel@mindpipe>

* Lee Revell (rlrevell@joe-job.com) wrote:
> On Fri, 2005-07-29 at 13:51 -0700, Chris Wright wrote:
> > * Chris Wright (chrisw@osdl.org) wrote:
> > > Yes, this requires updated pam patch.
> > 
> > Here's the updated pam patch.  I left the lower end at 0 rather than 1,
> > since it's no harm.
> >  
> > +/* Hack to test new rlimit values */
> 
> Does this still apply?  If so what would a better solution look like?

The better solution is to make sure you have new enough glibc-kernheaders
to pick up those values directly from resource.h and drop that hunk.  On
my systems, it's still needed even with rawhide headers.

thanks,
-chris

  reply	other threads:[~2005-07-29 21:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-28 15:04 Michael Kerrisk
2005-07-28 17:43 ` Andrew Morton
2005-07-29 11:29   ` [PATCH] MAINTAINERS record -- MAN-PAGES Michael Kerrisk
2005-07-29  6:13 ` Broke nice range for RLIMIT NICE Matt Mackall
2005-07-29  8:38   ` Ingo Molnar
2005-07-29 10:42     ` Michael Kerrisk
2005-07-29 14:50       ` Nix
2005-07-29 15:14         ` Michael Kerrisk
2005-07-29 20:57           ` Nix
2005-07-29 10:40   ` Michael Kerrisk
2005-07-29 20:18   ` Chris Wright
2005-07-29 20:51     ` Chris Wright
2005-07-29 21:02       ` Lee Revell
2005-07-29 21:07         ` Chris Wright [this message]
2005-08-15 20:13   ` [PATCH] Fix " Matt Mackall

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=20050729210756.GK19052@shell0.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.kerrisk@gmx.net \
    --cc=mingo@elte.hu \
    --cc=mpm@selenic.com \
    --cc=mtk-manpages@gmx.net \
    --cc=rlrevell@joe-job.com \
    /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
Powered by JetHome