From: Karel Zak <kzak@redhat.com>
To: Bernhard Voelker <mail@bernhard-voelker.de>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH 04/15] prlimit: add warning diagnostic when attempting to change prlimit's limits
Date: Wed, 16 Nov 2011 13:45:37 +0100 [thread overview]
Message-ID: <20111116124537.GD7916@nb.net.home> (raw)
In-Reply-To: <4EC0735B.2010504@bernhard-voelker.de>
On Mon, Nov 14, 2011 at 02:48:11AM +0100, Bernhard Voelker wrote:
> + if (lims[i].modify) {
> + if (!pid)
> + warnx(_("setting limits of the prlimit process is pointless"));
Well, I don't think that we want such warnings in our utils :-) Let's
inform users about errors, the rest should be described in man pages.
Anyway, it would be nice to have something like:
prlimit --nofile=1000 /bin/program
so somewhere after show_limits() should be exec().
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2011-11-16 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 1:48 [PATCH 04/15] prlimit: add warning diagnostic when attempting to change prlimit's limits Bernhard Voelker
2011-11-16 12:45 ` Karel Zak [this message]
2011-11-16 15:05 ` Bernhard Voelker
2011-11-16 15:55 ` Karel Zak
2011-11-16 15:05 ` Bernhard Voelker
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=20111116124537.GD7916@nb.net.home \
--to=kzak@redhat.com \
--cc=mail@bernhard-voelker.de \
--cc=util-linux@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.