From: Davidlohr Bueso <dave@gnu.org>
To: Bernhard Voelker <mail@bernhard-voelker.de>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH 00/15] prlimit
Date: Mon, 14 Nov 2011 11:56:27 +0100 [thread overview]
Message-ID: <1321268187.8015.4.camel@offworld> (raw)
In-Reply-To: <4EC07330.5050406@bernhard-voelker.de>
On Mon, 2011-11-14 at 02:47 +0100, Bernhard Voelker wrote:
> prlimit was not very graceful regarding option parsing.
>
> The central change of this series is done in [PATCH 11/15]
> which changes the way the lims array is used/filled.
> Others prepare the code to have a smaller main patch,
> or fix problems which arouse from the different use
> of the lims array.
>
> [PATCH 01/15] prlimit: show all limits if called without options
> [PATCH 02/15] prlimit: add opt_id array to match short options to limit ids
> [PATCH 03/15] prlimit: fix diagnostic when setting current PIDs
> resources fails
> [PATCH 04/15] prlimit: add warning diagnostic when attempting to change
> prlimit's limits
> [PATCH 05/15] prlimit: fix diagnostic when setting a limit fails
> [PATCH 06/15] prlimit: enhance diagnostic when changing a limit fails:
> add limit name
> [PATCH 07/15] prlimit: fix case when getting missing limit is needed and
> PID is given later
> [PATCH 08/15] prlimit: give better diagnostic for illegal hard limit case
> [PATCH 09/15] prlimit: fix typo in man page, option --verbose
> [PATCH 10/15] prlimit: refactor code: separate modify and show clearly
> [PATCH 11/15] prlimit: avoid segfault due to array-out-of-bounds error
> [PATCH 12/15] prlimit: add note to man page that setting limits without
> --pid is pointless.
> [PATCH 13/15] prlimit: enhance examples section of the man page
> [PATCH 14/15] prlimit: avoid prlimit syscalls for limits unless to
> modify or to show
> [PATCH 15/15] prlimit: fix displaying of modified limits
>
> I hope I didn't screw up too much. Please let me know what you think
> about it.
Thanks for looking into this, this is a very new program that needs as
much testing as possible before the 2.21 release.
>
> Have a nice day,
> Berny
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe util-linux" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2011-11-14 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 1:47 [PATCH 00/15] prlimit Bernhard Voelker
2011-11-14 10:56 ` Davidlohr Bueso [this message]
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=1321268187.8015.4.camel@offworld \
--to=dave@gnu.org \
--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 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).