Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 24 Oct 2002 12:40:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 24 Oct 2002 12:40:45 -0400 Received: from [206.124.139.154] ([206.124.139.154]:40205 "EHLO grieg.holmsjoen.com") by vger.kernel.org with ESMTP id ; Thu, 24 Oct 2002 12:40:44 -0400 Date: Thu, 24 Oct 2002 09:46:13 -0700 From: Randolph Bentson To: Frank Cornelis Cc: linux-kernel@vger.kernel.org, Frank.Cornelis@elis.rug.ac.be Subject: Re: Resource limits Message-ID: <20021024094613.A2727@grieg.holmsjoen.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from fcorneli@elis.rug.ac.be on Thu, Oct 24, 2002 at 02:13:01PM +0200 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1188 Lines: 24 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 - 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/