On 4 April 2016 at 10:07, Ruediger Meier <sweet_f_a@xxxxxx> wrote: > On Monday 04 April 2016, Karel Zak wrote: >> On Mon, Apr 04, 2016 at 02:21:00AM +0200, Karel Zak wrote: >> > On Sun, Apr 03, 2016 at 09:35:27AM +0100, Sami Kerola wrote: >> > > These options are expecting an argument, and the long options >> > > struct already required them. >> > >> > Good catch, but deadline and runtime should be optional arguments >> > (it seems I have merged wrong version of my patch:-( >> >> Sorry, didn't read the patch correctly. You're right. Applied, >> thanks. > > BTW I like the coreutils convention that new options with optional > arguments should be long options only. This is less confusing for the > users. Makes sense, and if Karel agrees Documentation/* files need updating. BTW the debian bug 791707 that was the reason why I even started to look chrt is pretty good indication the command is not easy to use or understand. To me the command is pretty unintuitive, for example $ chrt --pid --rt 0 foobar $$ is perfectly OK way to change scheduling policy of the running shell, and foobar is ignored. I don't quite understand why the --pid makes only the last argument to be used, while it could use all arguments the getopts() did eat. But even so the interface stays quirky as the argument order is $ chrt <options> <priority> <target> for example $ chrt --pid 0 $$ But fixing that cannot be done without breaking ABI, and such change cannot be approved. So should the util-linux v2.29 (or perhaps v3.0 as the numbers are getting a bit large) have new tools: $ rtctl $ lsrt Where the former has expected interface using options as people normally see them. For example: $ rtctl --priority 0 --policy rt --exec 'ls /etc' --pid $$ In above --exec or --pid can be used more than once, but 'settings' type options should not be allowed more than one instance to avoid confusions. And 'lsrt' would be for displaying the stuff rtctl is controlling. Comments? -- Sami Kerola http://www.iki.fi/kerolasa/ -- 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
