From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: riel@conectiva.com.br (Rik van Riel)
Cc: szaka@f-secure.com (Szabolcs Szakacsits),
mag@fbab.net ("Magnus Naeslund(f)"),
viro@math.psu.edu (Alexander Viro),
linux-kernel@vger.kernel.org (linux-kernel),
alan@lxorguk.ukuu.org.uk (Alan Cox)
Subject: Re: 2.4.8 Resource leaks + limits
Date: Sat, 18 Aug 2001 23:34:31 +0100 (BST) [thread overview]
Message-ID: <E15YEfn-0001oz-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.33L.0108181218380.5646-100000@imladris.rielhome.conectiva> from "Rik van Riel" at Aug 18, 2001 12:20:26 PM
>
> On Sat, 18 Aug 2001, Szabolcs Szakacsits wrote:
> > On Fri, 17 Aug 2001, Rik van Riel wrote:
> > > The fix is to disable the check for RLIMIT_NPROC in
> > > kernel/fork.c when the user is root. I made this patch
>
> > Everybody told him, including Alan, go away and fix PAM. He went away
> > and fixed PAM in 2 days. Up to day none of the main distributions ship
> > the correct[ly configured] PAM, so the problem still bites. Feel free
> > to rebut me.
>
> Wouldn't that involve fixing login, sshd, and all other
> programs using pam to set the limits before fork()ing ?
>
> I know the pam library is responsible for setting the
> user limits, but it's the program linked to libpam which
> is responsible for the order in which the other things
> are done, right ?
>
> (then again, I don't know enough about the userspace side
> of things here, I'd be happy if somebody could enlighten
> me)
>
> cheers,
>
> Rik
> --
> IA64: a worthy successor to i860.
>
> http://www.surriel.com/ http://distro.conectiva.com/
>
> Send all your spam to aardvark@nl.linux.org (spam digging piggy)
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2001-08-18 22:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33L.0108171818040.2277-100000@duckman.distro.conectiva>
2001-08-18 14:53 ` 2.4.8 Resource leaks + limits Magnus Naeslund(f)
2001-08-18 15:24 ` Szabolcs Szakacsits
2001-08-18 15:20 ` Rik van Riel
2001-08-18 22:34 ` Alan Cox [this message]
2001-08-18 22:35 ` Alan Cox
[not found] <no.id>
2001-08-15 11:40 ` Alan Cox
2001-08-15 16:53 ` Linus Torvalds
2001-08-15 18:51 ` Alan Cox
2001-08-15 19:57 ` Ingo Oeser
2001-08-15 20:15 ` Alan Cox
2001-08-15 21:30 ` Jesse Pollard
2001-08-15 20:57 ` Anton Altaparmakov
2001-08-16 1:12 ` Jesse Pollard
2001-08-15 22:14 ` Horst von Brand
2001-08-15 5:11 Magnus Naeslund(f)
2001-08-15 5:32 ` Linus Torvalds
2001-08-15 5:42 ` Ulrich Drepper
2001-08-15 8:31 ` Nadav Har'El
2001-08-15 5:43 ` dmaynor
2001-08-15 5:56 ` J Sloan
2001-08-15 6:59 ` Brian
2001-08-15 7:26 ` J Sloan
2001-08-15 13:51 ` Admin Mailing Lists
2001-08-15 14:12 ` dmaynor
2001-08-15 16:04 ` Alan Cox
2001-08-17 22:01 ` Rik van Riel
2001-08-17 22:08 ` Alan Cox
2001-08-17 23:25 ` Rik van Riel
2001-08-15 6:05 ` Magnus Naeslund(f)
2001-08-15 6:28 ` Alexander Viro
2001-08-15 7:24 ` Magnus Naeslund(f)
2001-08-15 14:21 ` Szabolcs Szakacsits
2001-08-15 14:20 ` Magnus Naeslund(f)
2001-08-16 19:41 ` Szabolcs Szakacsits
2001-08-16 19:54 ` Szabolcs Szakacsits
2001-08-17 15:56 ` Magnus Naeslund(f)
2001-08-15 15:00 ` Tobias Ringstrom
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=E15YEfn-0001oz-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mag@fbab.net \
--cc=riel@conectiva.com.br \
--cc=szaka@f-secure.com \
--cc=viro@math.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).