From: Alejandro Colomar <alx.manpages@gmail.com>
To: GNU C Library <libc-alpha@sourceware.org>
Cc: linux-man@vger.kernel.org, i+linux@1a-insec.net,
Alejandro Colomar <alx@kernel.org>
Subject: Re: [patch] nice.2: wfix
Date: Sun, 11 Dec 2022 18:33:36 +0100 [thread overview]
Message-ID: <aa61a91d-abc7-fae2-0494-9842b6081bb5@gmail.com> (raw)
In-Reply-To: <53fb2366-517c-9f76-982f-ac2d16d3476c@1a-insec.net>
[-- Attachment #1.1: Type: text/plain, Size: 1206 bytes --]
Hi glibc developers,
On 11/2/22 02:50, i+linux@1a-insec.net wrote:
> nice(2) in glibc uses `setpriority(PRIO_PROCESS, x)`. I think "thread" means
> pthread more, so "process" is the better word here.
>
> The patch is below:
>
>
> From 835c33dbc72abec02d49a5ac6b1b16e4d39a599b Mon Sep 17 00:00:00 2001
> From: Locria Cyber <74560659+locriacyber@users.noreply.github.com>
> Date: Tue, 1 Nov 2022 06:10:16 +0000
> Subject: [PATCH] nice.2 tfix
> Signed-off-by: Locria Cyber <i+linux@1a.insec.net>
I never used this syscall. Could any of you please review this patch?
Cheers,
Alex
>
> ---
> man2/nice.2 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man2/nice.2 b/man2/nice.2
> index f4e2406..2ecd743 100644
> --- a/man2/nice.2
> +++ b/man2/nice.2
> @@ -36,7 +36,7 @@ Feature Test Macro Requirements for glibc (see
> .BR nice ()
> adds
> .I inc
> -to the nice value for the calling thread.
> +to the nice value for the calling process.
> (A higher nice value means a lower priority.)
> .PP
> The range of the nice value is +19 (low priority) to \-20 (high priority).
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next parent reply other threads:[~2022-12-11 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53fb2366-517c-9f76-982f-ac2d16d3476c@1a-insec.net>
2022-12-11 17:33 ` Alejandro Colomar [this message]
2022-12-14 15:28 ` Jakub Wilk
2022-12-14 17:38 ` Alejandro Colomar
2022-12-14 17:39 ` Alejandro Colomar
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=aa61a91d-abc7-fae2-0494-9842b6081bb5@gmail.com \
--to=alx.manpages@gmail.com \
--cc=alx@kernel.org \
--cc=i+linux@1a-insec.net \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@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 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).