From: Gioele Barabucci <gioele@svario.it>
To: dash@vger.kernel.org
Subject: Re: [PATCH] man: Document ulimit -v
Date: Thu, 21 Jan 2016 08:25:59 +0100 [thread overview]
Message-ID: <n7q168$u95$1@ger.gmane.org> (raw)
In-Reply-To: <20160121050323.GA4908@gondor.apana.org.au>
On 21/01/2016 06:03, Herbert Xu wrote:
> Jérémie Courrèges-Anglas <jca@wxcvbn.org> wrote:
>> Gioele Barabucci <gioele@svario.it> 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 [1] since 1997 [2], 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).
Regards,
[1] http://pubs.opengroup.org/onlinepubs/9699919799/functions/setrlimit.html
[2] http://pubs.opengroup.org/onlinepubs/7908799/xsh/sysresource.h.html
--
Gioele Barabucci <gioele@svario.it>
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
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='n7q168$u95$1@ger.gmane.org' \
--to=gioele@svario.it \
--cc=dash@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.