From: "Ram Gupta" <ram.gupta5@gmail.com>
To: "linux mailing-list" <linux-kernel@vger.kernel.org>
Subject: support for limit of open file descriptors for a child process
Date: Thu, 14 Sep 2006 10:21:03 -0500 [thread overview]
Message-ID: <728201270609140821l7cf30578y2f45479b03e77f64@mail.gmail.com> (raw)
Hi,
I came across a problem regarding the issue of number of open
file descriptors.The scenario is as below.
I have a controlling process which launches other different
apllication including third party ones. It also enforces various
resource limits including number of open file descriptors. This
process forks & reads the resource limits from a configuration files,
applies the resource limits & then execs for the corresponding
application. The process has its own various number of open file
descriptors. If the limit of open file descriptor for the child
application is less than the number of file descriptors of the parent
process, then the child application file can not be opened & exec
fails in this case.
I searched solution for this problem but could not find an existing
way to solve it. I thought of couple of ways to do it. One idea is to
create another flag for clone which makes it not to inherit the open
file descriptors & use clone with that flag instead of fork .The other
approach is to create a new system call & parent process can call that
system call before calling the setrlimit.
I am looking for your opinion about the better way . Further if it is helpful
then I can submit the patch also.
Thanks in advance
regards
Ram Gupta
next reply other threads:[~2006-09-14 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 15:21 Ram Gupta [this message]
2006-09-14 15:28 ` Bernd Petrovitsch
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=728201270609140821l7cf30578y2f45479b03e77f64@mail.gmail.com \
--to=ram.gupta5@gmail.com \
--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
all inboxes | Powered by JetHome®