From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: setrlimit always fails
Date: Fri, 12 Feb 2021 10:12:33 +0100 [thread overview]
Message-ID: <20210212091233.GG4251@calimero.vinschen.de> (raw)
In-Reply-To: <42b30732-9aee-454e-3359-92a82ef09f0d@SystematicSw.ab.ca>
On Feb 12 00:26, Brian Inglis wrote:
> On 2021-02-11 19:06, Ken Brown via Cygwin wrote:
> > On 2/11/2021 10:23 AM, Patrick Chkoreff wrote:
> > > I'm trying to use setrlimit to impose limits on various resources such
> > > as CPU time and memory. The call to setrlimit always fails. I've
> > > distilled this into the following example test.c:
> > [...]
> > > if (setrlimit(RLIMIT_CPU,&rlim) < 0)
> > [...]
> > > setrlimit: Invalid argument
> >
> > Cygwin's setrlimit only supports a few resources, as you can see in the source:
> >
> > https://cygwin.com/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/resource.cc;h=97777e9d223466b7635b990d6c9e0bfb9e2e9a46;hb=HEAD#l201
>
> In that case could I suggest:
>
> /usr/share/doc/cygwin-doc/html/cygwin-api/compatibility.html#std-susv4
> https://cygwin.com/cygwin-api/compatibility.html#std-susv4
>
> in https://cygwin.com/git/?p=newlib-cygwin.git;a=blob;f=winsup/doc/posix.xml
>
> get/setrlimit entries should be annotated with:
https://cygwin.com/acronyms/#PGA
Corinna
--
Corinna Vinschen
Cygwin Maintainer
next prev parent reply other threads:[~2021-02-12 9:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 15:23 Patrick Chkoreff
2021-02-12 2:06 ` Ken Brown
2021-02-12 7:26 ` Brian Inglis
2021-02-12 9:12 ` Corinna Vinschen [this message]
2021-02-12 18:56 ` Brian Inglis
2021-02-12 20:38 ` Brian Inglis
2021-02-12 15:11 ` Patrick Chkoreff
2021-02-15 9:14 ` Corinna Vinschen
2021-02-15 19:54 ` Patrick Chkoreff
2021-02-15 20:48 ` Corinna Vinschen
2021-02-16 14:53 ` Patrick Chkoreff
2021-02-16 15:22 ` Marco Atzeri
2021-02-16 18:33 ` Brian Inglis
2021-02-12 9:11 ` Corinna Vinschen
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=20210212091233.GG4251@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).