|
Notice that the syntax of renice is not consistent among all Unix/Linux systems. For instance, on my Mac, the documentation says that -n means that the number following will be an increment, whereas the same man-page on my Linux virtual machine the implication of the text is that it is an extraneous and meaningless keyword.
It certainly seems possible that release-5 vs. release-7 of RHEL might have changed the syntax and/or the interpretation of this command at some point in time. Check carefully that the documentation is, or isn't, the same. The Linux scheduler has changed quite substantially between releases.
A little puzzled why it isn't letting you, as the superuser, set the priority to -10.
... although here I would insert the usual caveats to the effect that negative priorities, in particular, can cause trouble. As for myself, I only use positive priorities, to designate "batch job type" activities. That is to say: "if a user-interface (UI) mouse-click message arrives right now, should I or should I not interrupt you?" And, that's about the full extent of it. Among the pool of "processes that are RUNNABLE right now," I don't attempt to pick favorites. Instead, I fairly-loosely just try to sort out "the ones who can afford to wait."
"Generally, broad-brushed, speaking," nearly all dispatcher workloads are "I/O-bound," not "CPU," and, by their very nature, forever they will continue to be. So, "niceness" is only of marginal usefulness most of the time.
Last edited by sundialsvcs; 12-12-2016 at 01:25 PM.
|
