On Fri, Jul 22, 2011 at 10:09:57AM +0200, Voelker, Bernhard wrote:
> Since 7ab08ba3e5e6f161b93ff2b3b7d5b18dc7b44510, ionice requires a "scheduling".
>
> $ schedutils/ionice 123
> ionice: scheduling for the COMMAND not specified
>
> As `ionice` is the sister of `nice`, I question why a certain prio/class is needed.
> What's wrong with not passing a certain prio/class?
Good point, I'll fix it.
> Second, doesn't this break existing scripts which rely on "123" being executed?
It has never been supported:
$ ionice 123
none: prio 4
ionice: ioprio_get failed: No such process
Unfortunately, the 123 has been always interpreted as PID, not as
COMMAND. The another bug is that without -p the ioprio_get() has been
called two times, the "none: prio 4" is for PID=0 ;-)
I'll improve the behavior:
ionice : print the current I/O prio.
ionice <COMMAND> : exec command with default (best-effort) class
ionice -p PID [...] : return info about the PID(s)
ionice -c CLASS COMMAND : exec command with the class
ionice -c CLASS -p PID [...] : modify PID(s) class
Comments?
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
