Re: Broke nice range for RLIMIT NICE

On Fri, 2005-07-29 at 13:51 -0700, Chris Wright wrote:
> * Chris Wright ([email protected]) 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?

Lee

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: Broke nice range for RLIMIT NICE
    • From: Chris Wright <[email protected]>

• References:
  • Broke nice range for RLIMIT NICE
    • From: "Michael Kerrisk" <[email protected]>
  • Re: Broke nice range for RLIMIT NICE
    • From: Matt Mackall <[email protected]>
  • Re: Broke nice range for RLIMIT NICE
    • From: Chris Wright <[email protected]>
  • Re: Broke nice range for RLIMIT NICE
    • From: Chris Wright <[email protected]>

• Prev by Date: Re: Why dump_stack results different so much?
• Next by Date: RE: [PATCH] i386 io_apic.c: Memorize at bootup where the i8259 is connected
• Previous by thread: Re: Broke nice range for RLIMIT NICE
• Next by thread: Re: Broke nice range for RLIMIT NICE
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]