public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randolph Bentson <bentson@grieg.holmsjoen.com>
To: Frank Cornelis <fcorneli@elis.rug.ac.be>
Cc: linux-kernel@vger.kernel.org, Frank.Cornelis@elis.rug.ac.be
Subject: Re: Resource limits
Date: Thu, 24 Oct 2002 09:46:13 -0700	[thread overview]
Message-ID: <20021024094613.A2727@grieg.holmsjoen.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0210241357350.14267-100000@trappist.elis.rug.ac.be>; from fcorneli@elis.rug.ac.be on Thu, Oct 24, 2002 at 02:13:01PM +0200

On Thu, Oct 24, 2002 at 02:13:01PM +0200, Frank Cornelis wrote:
> This way a parent process is able to temporary drop some of its
> limits in order to make a restricted child process and restore
> its resource limits afterwards. Currenly it is not possible to
> make a child process with smaller resource limits than the parent
> process without the parent process losing its (hard) max limits
> (As far as I know, correct me if I'm wrong).

Hmm, this statement suggests the author misunderstands the Unix-based
conventional use of the separated fork/exec calls.  After the fork
call, the child process is still running code common to the parent,
but typically (by convention) a different leg of an if-then-else
statement.  This code in this leg can reduce resource limits before
make an exec call to start a new program.  The parent's limits are
not affected.  There's no need to change the kernel.

-- 
Randolph Bentson
bentson@holmsjoen.com

  reply	other threads:[~2002-10-24 16:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-24 12:13 Resource limits Frank Cornelis
2002-10-24 16:46 ` Randolph Bentson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-25 14:12 Al Boldi
2005-09-26  3:36 ` Rik van Riel
2005-09-26 14:18   ` Al Boldi
2005-09-26 15:56     ` Neil Horman
2005-09-26 17:32       ` Al Boldi
2005-09-26 17:51         ` Neil Horman
2005-09-26 20:26           ` Al Boldi
2005-09-27  1:05             ` Neil Horman
2005-09-27  5:08               ` Al Boldi
2005-09-27 12:08                 ` Neil Horman
2005-09-27 13:42                   ` Al Boldi
2005-09-27 14:36                     ` Neil Horman
2005-09-27 15:50                       ` Al Boldi
2005-09-27 17:25                         ` Neil Horman
2005-09-27 21:35                 ` Chandra Seetharaman
2005-09-26 12:28 ` Neil Horman
2005-09-26 14:44 ` Roger Heflin
2005-09-26 17:11   ` Alan Cox
2005-09-26 17:32     ` Al Boldi
2005-09-26 21:21     ` Roger Heflin
2005-09-27  3:50   ` Coywolf Qi Hunt
2005-09-26 19:07 ` Matthew Helsley

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=20021024094613.A2727@grieg.holmsjoen.com \
    --to=bentson@grieg.holmsjoen.com \
    --cc=Frank.Cornelis@elis.rug.ac.be \
    --cc=fcorneli@elis.rug.ac.be \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox