From: Benno Schulenberg <bensberg@telfort.nl>
To: util-linux@vger.kernel.org
Cc: Madadi Vineeth Reddy <vineethr@linux.ibm.com>
Subject: [PATCH 2/4] chrt: (man,usage) mark the priority value as optional in the synopses
Date: Tue, 5 Aug 2025 11:24:41 +0200 [thread overview]
Message-ID: <20250805092443.5847-2-bensberg@telfort.nl> (raw)
In-Reply-To: <20250805092443.5847-1-bensberg@telfort.nl>
The priority value is optional in some cases, so it cannot be listed
as required.
CC: Madadi Vineeth Reddy <vineethr@linux.ibm.com>
Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
---
schedutils/chrt.1.adoc | 2 +-
schedutils/chrt.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/schedutils/chrt.1.adoc b/schedutils/chrt.1.adoc
index 3f67b13bb..c8278463a 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 e07284e41..de1898160 100644
--- a/schedutils/chrt.c
+++ b/schedutils/chrt.c
@@ -60,8 +60,8 @@ 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> [<argument>...]\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);
--
2.48.2
next prev parent reply other threads:[~2025-08-05 9:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 9:24 [PATCH 1/4] chrt: produce better error message for missing priority with implied -r Benno Schulenberg
2025-08-05 9:24 ` Benno Schulenberg [this message]
2025-08-05 9:24 ` [PATCH 3/4] chrt: (man) improve wording and markup of some examples Benno Schulenberg
2025-08-05 9:24 ` [PATCH 4/4] chrt: (man,usage) put --pid first in synopses and examples, for clarity Benno Schulenberg
2025-08-11 9:23 ` [PATCH 1/4] chrt: produce better error message for missing priority with implied -r 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=20250805092443.5847-2-bensberg@telfort.nl \
--to=bensberg@telfort.nl \
--cc=util-linux@vger.kernel.org \
--cc=vineethr@linux.ibm.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