Your message dated Tue, 18 Feb 2014 13:34:51 -0500 with message-id <[email protected]> and subject line util-linux: chrt fails to set policy on new commands has caused the Debian Bug report #502537, regarding util-linux: chrt fails to set policy on new commands to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 502537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502537 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: util-linux Version: 2.13.1.1-1 Hello, chrt cannot set the scheduling policy for a command tu run: root@darkside:~# chrt 19 /bin/echo foo foo root@darkside:~# chrt -b 19 /bin/echo foo sched_setscheduler: Invalid argument failed to set pid 0's policy schedtool, for example, can do that. And btw... some schedulers don't actually need a prio, this is not supported as well, even though the usage suggests it: root@darkside:~# chrt -h 2>&1 | grep ^usage usage: chrt [options] [prio] [pid | cmd [args...]] root@darkside:~# chrt -b /bin/echo foo execvp: No such file or directory failed to execute foo regards Mario -- What I need is an exact list of specific unknown problems we might encounter. -- Manager, Lykes Lines Shipping
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message --------BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Upstream considers this to not be a bug because chrt is a low level wrapper around the setpriority() system call, and it requires a priority argument, and that it be zero for idle and batch classes. At some point in the future, the kernel may accept other values. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTA6fLAAoJEI5FoCIzSKrwvOsH/ig1otm0sDQVa9E2BD2r+tsb ZtpOlJkgYK0qC7hXFCFtz2IFFC/0Qzc317j2p3vUW1U6vAW4neg2OXDpCbnhi1FD EAFXQTtqLk2QO3tczp7ILk5J6qgbhUbLfavBSXN118ODJKhyStIWVB6aLRIFxix3 kkR2MmyWw1nZfLPgTuJJlNv8IynLBbxvIQFOScj6inj81awvTY8joLnAga7/EQmk KAJGneF46wMDD3sn9qC9fLQovShgvExbxYAat1zg9sShWJXVtgxOKJ16AHT9TjoO /I+xDIlGX1jCDzmtF1ayv6UpPbb6M7UZN6a+EU3Dc7T70zNpBfMvhoH174Bn5U8= =UnHy -----END PGP SIGNATURE-----
--- End Message ---
