diff options
author | delphij <delphij@FreeBSD.org> | 2011-12-27 20:03:57 +0000 |
---|---|---|
committer | delphij <delphij@FreeBSD.org> | 2011-12-27 20:03:57 +0000 |
commit | 2fadf62dc19d1aac7d5cb336e9585cbaa69fcf80 (patch) | |
tree | abed5e79378ad7071ebc59fa98be68ae43e64d22 /lib/libcompiler_rt/__sync_fetch_and_and_8.c | |
parent | ab0468cff534cd1851c81424c4d6c24e77927937 (diff) | |
download | FreeBSD-src-2fadf62dc19d1aac7d5cb336e9585cbaa69fcf80.zip FreeBSD-src-2fadf62dc19d1aac7d5cb336e9585cbaa69fcf80.tar.gz |
- Fail when the utility is not invoked as rtprio nor idprio.
- 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
Diffstat (limited to 'lib/libcompiler_rt/__sync_fetch_and_and_8.c')
0 files changed, 0 insertions, 0 deletions