Process Priority does change

[Lalit Seth]

Hi,

I have processes running at priority 152, eating cpu as hell.

As far as I can notice, the priority of those processes doesn't change, even with a nice value of 39.

Using the 'renice' command.

What can be the cause. How this can be overcomed.

Many Thanks

[RAC_1]

Any process, that is in priority range of 128-153 is in kernel mode. What it means is it is un-signalable and waiting for something in kernel mode. You can not do anything about it. You have a look at "what exactly it is wainting for" Run glance -B, glance , select a process and check the wait state.

It could be a hung process and can not be killed even with -9 signal.

Anil

[Lalit Seth]

I am sure that it is not an hung process it does rsponse on the actions.

Also, its status in not wait instead it is displayed are run under 'top'.

[Steven E. Protter]

Can you post the commands you used and the response. Then perhaps someone can suggest revisions.

If nothing else is running, it doesn't matter what nice value you give the process its going to eat up the machine.

SEP

[Mark Greene_1]

Check the output from ipcs -ca|pg specificially the CPID and LPID cols. If the PID of the process in question appears in the list a bunch of times, you've got semaphore contention, shared memory contention, or both.

Check out the swapinfo -at command as well.

mark