behavior of `chrt` changed when specifying a command

Benno Schulenberg <[email protected]> Wed, 25 Jun 2025 16:42:54 +0200

Newsgroups	org.kernel.vger.util-linux
Message-ID	<[email protected]>

Before the recent changes to chrt.c (commit e7a2d62434 and earlier),
one could let `chrt` run a command while specifying only a priority,
leaving `chrt` to pick SCHED_RR as the default policy:

   chrt 12 grep boo README

This would print one line from the README.

But running that command in current git gives:

   chrt: unsupported priority value for the policy: 0: see --max for valid range

One has to specify the policy explicitly for the command to work:

   chrt -r 12 grep boo README

If that is intentional, then the synopsis needs to be adjusted to show the need
for a policy option when wanting to run a command with `chrt`.


Benno

OpenPGP_signature.asc (application/pgp-signature, 840 B)