From: "Michael Kerrisk" <mtk-manpages@gmx.net>
To: Nix <nix@esperi.org.uk>
Cc: mingo@elte.hu, mpm@selenic.com, linux-kernel@vger.kernel.org,
michael.kerrisk@gmx.net, akpm@osdl.org, chrisw@osdl.org
Subject: Re: Broke nice range for RLIMIT NICE
Date: Fri, 29 Jul 2005 17:14:44 +0200 (MEST) [thread overview]
Message-ID: <12213.1122650084@www71.gmx.net> (raw)
In-Reply-To: 87u0idhdju.fsf@amaterasu.srvr.nix
> On 29 Jul 2005, Michael Kerrisk stated:
> > Yes, as noted in my earlier message -- at the moment RLIMIT_NICE
> > still isn't in the current glibc snapshot...
>
> According to traffic on libc-hacker, Ulrich committed it on Jun 20
> (along with RLIMIT_RTPRIO support).
I (now) see the message that you mean on libc-hacker, nevertheless,
looking at the glibc-2.3-20050725 snapshot, these two constants do
not appear anywhere. (Strange!)
Cheers,
Michael
--
Michael Kerrisk
maintainer of Linux man pages Sections 2, 3, 4, 5, and 7
Want to help with man page maintenance? Grab the latest
tarball at ftp://ftp.win.tue.nl/pub/linux-local/manpages/
and grep the source files for 'FIXME'.
next prev parent reply other threads:[~2005-07-29 15:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 15:04 Broke nice range for RLIMIT NICE Michael Kerrisk
2005-07-28 17:43 ` Andrew Morton
2005-07-29 11:29 ` [PATCH] MAINTAINERS record -- MAN-PAGES Michael Kerrisk
2005-07-29 6:13 ` Broke nice range for RLIMIT NICE Matt Mackall
2005-07-29 8:38 ` Ingo Molnar
2005-07-29 10:42 ` Michael Kerrisk
2005-07-29 14:50 ` Nix
2005-07-29 15:14 ` Michael Kerrisk [this message]
2005-07-29 20:57 ` Nix
2005-07-29 10:40 ` Michael Kerrisk
2005-07-29 20:18 ` Chris Wright
2005-07-29 20:51 ` Chris Wright
2005-07-29 21:02 ` Lee Revell
2005-07-29 21:07 ` Chris Wright
2005-08-15 20:13 ` [PATCH] Fix " Matt Mackall
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=12213.1122650084@www71.gmx.net \
--to=mtk-manpages@gmx.net \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.kerrisk@gmx.net \
--cc=mingo@elte.hu \
--cc=mpm@selenic.com \
--cc=nix@esperi.org.uk \
/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.