From: Gioele Barabucci <firstname.lastname@example.org>
Subject: Re: [PATCH] man: Document ulimit -v
Date: Thu, 21 Jan 2016 08:25:59 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
On 21/01/2016 06:03, Herbert Xu wrote:
> Jérémie Courrèges-Anglas <firstname.lastname@example.org> wrote:
>> Gioele Barabucci <email@example.com> writes:
>>> Document that `ulimit` can set the `RLIMIT_AS` limit (virtual memory) with
>>> the `-v` flag.
>> I don't know much about RLIMIT_AS, but I know that it isn't supported on
>> all systems where dash runs, eg OpenBSD. Maybe is it Linux-specific?
>> Anyway, it would be better if the manpage said that the -v flag may not
>> be implemented on all platforms.
>> The same could be said about ulimit -w. (I did not check the other flags).
> Rather than doing that we could just pass the manpage through
> cpp or some similar mechanism so that this becomes conditional.
I wonder how much it is worth the effort in this case.
RLIMIT_AS is defined by POSIX  since 1997 , so one can suppose
that it is available anywhere (indeed the man page of OpenBSD refers to
the missing RLIMIT_AS as a bug). If it is not available, an invocation
of `ulimit -v` will complain about the unknown option. We could just add
to the description "(not available on systems that lack support for
RLIMIT_AS, e.g. OpenBSD)".
Other cases like `-w` can be ignored: they manipulate non-standard
RLIMIT extensions that are no-ops on Linux since long ago (and I suppose
also in other systems).
Gioele Barabucci <firstname.lastname@example.org>
next prev parent reply other threads:[~2016-01-21 7:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 19:12 [PATCH] man: Document ulimit -v Gioele Barabucci
2016-01-20 18:02 ` Jérémie Courrèges-Anglas
2016-01-21 5:03 ` Herbert Xu
2016-01-21 7:25 ` Gioele Barabucci [this message]
2016-06-06 14:45 ` Herbert Xu
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).