All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank v Waveren <fvw@var.cx>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] no RLIMIT_NPROC for root, please
Date: Tue, 28 Nov 2000 23:13:34 +0100	[thread overview]
Message-ID: <20001128231334.A438@var.cx> (raw)
In-Reply-To: <20001128222040.H2680@sith.mimuw.edu.pl> <E140slT-000565-00@the-village.bc.nu>
In-Reply-To: <E140slT-000565-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Tue, Nov 28, 2000 at 09:58:14PM +0000

On Tue, Nov 28, 2000 at 09:58:14PM +0000, Alan Cox wrote:
> > Because you want to be able to `kill <pid>`?
> > And if you are over-limits you can't?
> Wrong. limit is a shell built in

I assume you mean kill is a shell builtin. Depending on your shell. :-).
It's still a real pain when you want to get the pid of the offending
proces(ses). You could of course do something like
for a in /proc/*; do echo -en "$a "; cat $a/cmdline; echo; done (it'll
barf a lot, but give a reasonable picture)...

Anyways, this is all not relevant, imho the whole point is moot.
"I don't like root having rlimits."
"So don't setrlimit root."

No reason to ditch functionality.

-- 

                        Frank v Waveren
                        fvw@[var.cx|stack.nl|chello.nl|dse.nl]
                        ICQ# 10074100
-
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/

  reply	other threads:[~2000-11-28 22:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-28 20:43 [PATCH] no RLIMIT_NPROC for root, please 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 [this message]
2000-11-28 23:23         ` Miquel van Smoorenburg
2000-11-28 21:54 ` Alan Cox
2000-11-29  0:34   ` Jan Rekorajski

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=20001128231334.A438@var.cx \
    --to=fvw@var.cx \
    --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.