>>On a Solaris 2.3 machine, both jobs get the same CPU percentage (near
>>50% on a otherwise idling machine), NO MATTER how nice they are, even
>>How do I change process priority in the normal (non-runtime) class ??
>Nice does set the process priority under Solaris 2, it just doesn't
>stay where you set it! :-(.
>The Solaris 2 process scheduler is a table-driven state machine. You
>can see the transition table by using the command "dispadmin -c TS -g".
>Although the tables shipped with Solaris 2.3 are different from 2.2,
>both of them are fully connected, meaning that a niced process that
>starts out at a particular priority will eventually migrate to the
>same priority as other (non-niced) processes.
>If you want nice to work as intended, you will have to write and
>install your own scheduler table, with disjoint sets of priorities,
>so that a process started in a particular set cannot escape from
>It doesn't seem like too much to ask for Sun to supply such a table, but
>I guess they have more important things to do.
So, before I try and reinvent the wheel, has anybody created a disjoint
table for solaris so that all jobs don't migrate to the same priority?
This seems like the way things hould have been set up.
If you have such a table, please post it, and/or mail it to me. Thanks
David Knight Tel: (518)-442-4204
Department of Atmospheric Science Fax: (518)-442-4494