From: Benno Schulenberg <bensberg@telfort.nl>
To: util-linux@vger.kernel.org
Subject: [PATCH 2/2] chrt: (man) mark "argument" as optional, and unabbreviate it in usage
Date: Wed, 25 Jun 2025 10:09:48 +0200 [thread overview]
Message-ID: <20250625080948.6064-2-bensberg@telfort.nl> (raw)
In-Reply-To: <20250625080948.6064-1-bensberg@telfort.nl>
Also, consistently uppercase "PID", to indicate it is an abbreviation,
and align the strings properly.
Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
---
schedutils/chrt.1.adoc | 2 +-
schedutils/chrt.c | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/schedutils/chrt.1.adoc b/schedutils/chrt.1.adoc
index 17d683ba7..3f67b13bb 100644
--- a/schedutils/chrt.1.adoc
+++ b/schedutils/chrt.1.adoc
@@ -38,7 +38,7 @@ chrt - manipulate the real-time attributes of a process
== SYNOPSIS
-*chrt* [options] _priority command argument_ ...
+*chrt* [options] _priority command_ [_argument_...]
*chrt* [options] *--pid* [_priority_] _PID_
diff --git a/schedutils/chrt.c b/schedutils/chrt.c
index 0bcdd1a1e..550cefe4d 100644
--- a/schedutils/chrt.c
+++ b/schedutils/chrt.c
@@ -60,11 +60,11 @@ static void __attribute__((__noreturn__)) usage(void)
fputs(_("Show or change the real-time scheduling attributes of a process.\n"), out);
fputs(USAGE_SEPARATOR, out);
fputs(_("Set policy:\n"
- " chrt [options] <priority> <command> [<arg>...]\n"
- " chrt [options] --pid <priority> <pid>\n"), out);
+ " chrt [options] <priority> <command> [<argument>...]\n"
+ " chrt [options] --pid <priority> <PID>\n"), out);
fputs(USAGE_SEPARATOR, out);
fputs(_("Get policy:\n"
- " chrt --pid <pid>\n"), out);
+ " chrt --pid <PID>\n"), out);
fputs(USAGE_SEPARATOR, out);
fputs(_("Policy options:\n"), out);
--
2.48.1
next prev parent reply other threads:[~2025-06-25 8:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 8:09 [PATCH 1/2] chrt: (man) correct the short form of --ext, from -d to -e Benno Schulenberg
2025-06-25 8:09 ` Benno Schulenberg [this message]
2025-07-01 15:55 ` Karel Zak
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=20250625080948.6064-2-bensberg@telfort.nl \
--to=bensberg@telfort.nl \
--cc=util-linux@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