From: "Nadav Har'El" <nyh@math.technion.ac.il>
To: Ulrich Drepper <drepper@cygnus.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
mag@fbab.net, linux-kernel@vger.kernel.org
Subject: Re: 2.4.8 Resource leaks + limits
Date: Wed, 15 Aug 2001 11:31:51 +0300 [thread overview]
Message-ID: <20010815113151.A28444@leeor.math.technion.ac.il> (raw)
In-Reply-To: <200108150532.f7F5WGq01653@penguin.transmeta.com> <m3snetq3po.fsf@otr.mynet>
In-Reply-To: <m3snetq3po.fsf@otr.mynet>; from drepper@redhat.com on Tue, Aug 14, 2001 at 10:42:11PM -0700
On Tue, Aug 14, 2001, Ulrich Drepper wrote about "Re: 2.4.8 Resource leaks + limits":
> Linus Torvalds <torvalds@transmeta.com> writes:
>
> > However, part of the problem is that because the limits haven't
> > historically existed, there is also no accepted and nice way of
> > setting the limits.
>
> This should be the least of the problems. Simply add new RLIMIT_*
> values[1] (and possibly [gs]etrlimit64 syscalls). The shell's ulimit
> command can easily pick those up. Non-standard, but every other
> solution will be, too.
I don't see how this would work without confusing users. ulimit currently
fits the model where limits are enforced per process, because each process
can have its own different limits.
If add per-user limits, what do you do if the user has several processes with
different per-user limits? You'll need to have "ulimit" and the likes set a
per-user limit shared by all processes of this user, and the last one
set by any process "wins" and takes effect. But this will not be expected by
the users who expect ulimits to effect only children processes (e.g., now it's
common to lower a limit and fork/exec a program which you want to limit).
So it's doable this way, but the manuals will have to be very clear as to
which limits are inherited how.
--
Nadav Har'El | Wednesday, Aug 15 2001, 26 Av 5761
nyh@math.technion.ac.il |-----------------------------------------
Phone: +972-53-245868, ICQ 13349191 |I used to work in a pickle factory, until
http://nadav.harel.org.il |I got canned.
next prev parent reply other threads:[~2001-08-15 8:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-15 5:11 2.4.8 Resource leaks + limits 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 [this message]
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
[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
[not found] <Pine.LNX.4.33L.0108171818040.2277-100000@duckman.distro.conectiva>
2001-08-18 14:53 ` 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
2001-08-18 22:35 ` Alan Cox
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=20010815113151.A28444@leeor.math.technion.ac.il \
--to=nyh@math.technion.ac.il \
--cc=drepper@cygnus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mag@fbab.net \
--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;
as well as URLs for NNTP newsgroup(s).