From: Jan Rekorajski <baggins@sith.mimuw.edu.pl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] no RLIMIT_NPROC for root, please
Date: Wed, 29 Nov 2000 01:34:59 +0100 [thread overview]
Message-ID: <20001129013459.B20515@sith.mimuw.edu.pl> (raw)
In-Reply-To: <20001128214309.F2680@sith.mimuw.edu.pl> <E140shP-00055W-00@the-village.bc.nu>
In-Reply-To: <E140shP-00055W-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Tue, Nov 28, 2000 at 09:54:00PM +0000
On Tue, 28 Nov 2000, Alan Cox wrote:
> > Why is RLIMIT_NPROC apllied to root(uid 0) processes? It's not kernel j=
> > ob to
> > prevent admin from shooting him/her self in the foot.
> >
> > root should be able to do fork() regardless of any limits,
> > and IMHO the following patch is the right thing.
>
> This patch is bogus. root can always raise their limit. But having root
> tasks by default not take out the box is good
OK, I just fix applications that assume root = no limits ;)
Jan
--
Jan Rękorajski | ALL SUSPECTS ARE GUILTY. PERIOD!
baggins<at>mimuw.edu.pl | OTHERWISE THEY WOULDN'T BE SUSPECTS, WOULD THEY?
BOFH, type MANIAC | -- TROOPS by Kevin Rubio
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-11-29 1:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-28 20:43 Jan Rekorajski
2000-11-28 20:52 ` Tigran Aivazian
2000-11-28 20:58 ` Tigran Aivazian
2000-11-28 21:11 ` Jan Rekorajski
2000-11-30 0:00 ` Pavel Machek
2000-11-30 21:24 ` Jan Rekorajski
2000-11-30 21:57 ` Tigran Aivazian
2000-11-28 21:08 ` Andreas Dilger
2000-11-28 21:11 ` Andreas Schwab
2000-11-28 21:20 ` Jan Rekorajski
2000-11-28 21:58 ` Alan Cox
2000-11-28 22:13 ` Frank v Waveren
2000-11-28 23:23 ` Miquel van Smoorenburg
2000-11-28 21:54 ` Alan Cox
2000-11-29 0:34 ` Jan Rekorajski [this message]
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=20001129013459.B20515@sith.mimuw.edu.pl \
--to=baggins@sith.mimuw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®