| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
this is a regression introduced with r228917.
PR: bin/154042
Submitted by: Bugs Beastie <bugsbeastie gmail.com>
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- use warnx() to tell the user whether a process is running in normal,
idle or realtime priority. with the old code it would have been possible
for another process to send data to stdout between
printf("%s: ", p);
and
printf("* priority\n");
and thus break the formatting.
- 'rtprio 10 -0' triggeres non-intuitive behavior. It would first set the
priority of itself to 10 *and* would then try to execute '-0'. Of course,
setting the priority of [id|rt]prio itself doesn't make a lot of sense,
but it is intuitive compared to the previous behavior.
- 'rtprio -t --1' will actually pass over the '-1' to rtprio(). Now
invoking rtprio like this will catch the wrong usage before passing
over the invalid argument to rtprio().
- Garrett Cooper suggested to add further diagnostics where the failure
occures, if execvp fails.
PR: bin/154042
Submitted by: arundel
MFC after: 1 month
|
|
|
|
|
|
|
| |
information in errno.
Noted by: Garrett Cooper <yanegomi gmail com>
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
Style.
Based on submission by: Eitan Adler <lists eitanadler com>, keramida
Reviewed by: jhb, keramida
MFC after: 1 week
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Submitted by: Jos.Backus@nl.origin-it.com
Correct execvp fail message in current
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been
insane otherwise.
|
|
|
|
| |
but substantially rewritten by me.
|
|
Submitted by: Henrik Vestergaard Draboel
|