From: Martin Steigerwald <ms@teamix.de>
To: <util-linux@vger.kernel.org>
Subject: chrt: inconsistency in --help
Date: Tue, 9 Jun 2015 10:37:46 +0200 [thread overview]
Message-ID: <716925135.onXIMLDpa0@merkaba> (raw)
Hi!
In wheezy I have (util-linux 2.20.1-5.3):
somehost:~$ chrt --help
chrt - manipulate real-time attributes of a process
Set policy:
chrt [options] <policy> <priority> {<pid> | <command> [<arg> ...]}
Get policy:
chrt [options] {<pid> | <command> [<arg> ...]}
And this works for a PID if I place "-p" with the options. Like this:
chrt -p -i 0 $$
chrt -pi 0 $$
chrt -i -p 0 $$
chrt -ip 0 $$
In Jessie I have(util-linux 2.25.2-6):
somehost:~$ chrt --help
chrt - manipulate real-time attributes of a process
Set policy:
chrt [options] [<policy>] <priority> [-p <pid> | <command> [<arg>...]]
Get policy:
chrt [options] -p <pid>
And this doesn´t work:
chrt -i 0 -p $$
chrt: failed to execute -p: No such file or directory
Suggestion:
1) Either make chrt command parsing more flexible (preffered)
2) or or even and change set policy to
Set policy:
chrt [options] [-p] [<policy>] <priority> [<pid> | <command> [<arg>...]]
But well second option separates -p from pid. So maybe option 1 is the way
to go.
What do you think?
Ciao,
--
Martin Steigerwald | Consultant / Trainer
teamix GmbH
Südwestpark 43
90449 Nürnberg
Tel.: +49 911 30999 55 | Fax: +49 911 30999 99
mail: martin.steigerwald@teamix.de | web: http://www.teamix.de | blog: http://blog.teamix.de
Amtsgericht Nürnberg, HRB 18320 | Geschäftsführer: Oliver Kügow, Richard Müller
***Nicht verpassen: NSX Roadshow "Optimierte Sicherheit für das moderne Rechenzentrum - Sicherheit im Wandel" mit teamix, TrendMicro und VMware***
Nürnberg 18.06. | München 02.07. | Frankfurt 16.07. | Stuttgart 23.07.
Jetzt anmelden: www.teamix.de/nsx-roadshow
next reply other threads:[~2015-06-09 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 8:37 Martin Steigerwald [this message]
2015-06-09 9:24 ` chrt: inconsistency in --help Karel Zak
2015-06-11 9:03 ` Benno Schulenberg
2015-06-15 13:09 ` 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=716925135.onXIMLDpa0@merkaba \
--to=ms@teamix.de \
--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