From: Jun T <takimoto-j@kba.biglobe.ne.jp>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] find RLIM_NLIMITS correctly on Cygwin
Date: Tue, 14 Jan 2020 13:44:01 +0900 [thread overview]
Message-ID: <3340070A-53DD-40F0-8363-A8C7D84702D3@kba.biglobe.ne.jp> (raw)
In-Reply-To: <c0580696-d917-4658-9c35-0af0e0625c67@www.fastmail.com>
> 2020/01/14 1:42, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> Jun T wrote on Mon, 13 Jan 2020 11:00 +00:00:
>>
>>> 2020/01/12 5:15, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>>>
>>> The part that's not clear to me is how we'd even know that «8» is a valid value for
>>> the first actual argument to getrlimit(). Currently, the code assumes that the
>>> values of RLIMIT_* macros are consecutive small integers, but that is not guaranteed
>>> by any standard, is it?
>>
>> There is no guarantee, but current version of ulimit builtin accepts any number
>> for -N (and output error). limit builtin accepts only the resource name,
>> and maybe we accept "unknonw8" only for getrlimit() but not for setrlimit()?
>
> Sorry, I don't follow. Why shouldn't we accept "unknown8" in the limit-setting syntaxes?
Sorry for my unclear English.
Why do you think that knowing "8" is a valid resource number is important?
I think we can just call {get, set}rlimit() with any resource number, but if you
think it better to avoid using questionable resource number, then we can avoid
calling setrlimit() that may actually change the limit of "unknown" resource.
But ulimit -N 8 can change the limit anyway, so I think we can call {get, set}rlimit()
with any resource number specified by the user.
next prev parent reply other threads:[~2020-01-14 4:44 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 10:39 Jun T
2020-01-08 21:33 ` Daniel Shahaf
2020-01-09 10:32 ` Jun T
2020-01-09 13:15 ` Daniel Shahaf
2020-01-10 10:24 ` Jun T
2020-01-11 20:15 ` Daniel Shahaf
2020-01-13 11:00 ` Jun T
2020-01-13 16:42 ` Daniel Shahaf
2020-01-14 4:44 ` Jun T [this message]
2020-01-14 16:25 ` Daniel Shahaf
2020-02-25 9:38 ` Jun T
2020-02-27 13:22 ` Daniel Shahaf
2020-02-27 18:46 ` Mikael Magnusson
2020-02-28 8:42 ` Jun T
2020-02-28 14:19 ` Daniel Shahaf
2020-02-28 14:31 ` Daniel Shahaf
2020-03-03 9:23 ` Jun T
2020-03-04 19:29 ` Daniel Shahaf
2020-03-05 10:26 ` Jun T
2020-03-05 14:58 ` Daniel Shahaf
2020-03-20 17:02 ` Daniel Shahaf
2020-03-20 17:20 ` Bart Schaefer
2020-03-20 17:39 ` Daniel Shahaf
2020-03-20 18:28 ` Daniel Shahaf
2020-03-20 18:36 ` Bart Schaefer
2020-03-20 19:38 ` Daniel Shahaf
2020-03-20 18:39 ` Bart Schaefer
2020-03-20 19:32 ` Daniel Shahaf
2020-03-20 19:18 ` Daniel Shahaf
2020-03-23 5:31 ` Jun T
2020-03-24 2:08 ` Daniel Shahaf
2020-03-23 5:41 ` Jun T
2020-03-24 1:33 ` Jun T
2020-03-24 2:43 ` Daniel Shahaf
2020-03-25 0:16 ` Jun T
2020-03-25 22:04 ` Daniel Shahaf
2020-03-25 23:42 ` [PATCH] find RLIM_NLIMITS correctly on CygwinjL Daniel Shahaf
2020-03-24 2:34 ` [PATCH] find RLIM_NLIMITS correctly on Cygwin Daniel Shahaf
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=3340070A-53DD-40F0-8363-A8C7D84702D3@kba.biglobe.ne.jp \
--to=takimoto-j@kba.biglobe.ne.jp \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).