[Info-vax] HIBertanting DECthreads process accrues CPU time.

[VAXman- at SendSpamHere.ORG]

In article <b1a94ca1-5582-4e4f-bd57-bda5be12067c at y26g2000yqd.googlegroups.com>, Hein RMS van den Heuvel <heinvandenheuvel at gmail.com> writes:
>Sandeeps contribution came after hundreds of lines of included text
>and thus was hard to find (for me at least)
>
>So as an attempt to a public service, here is just his reply text.
>Hein
>
>---- Sandeep -----
>
>When a threaded application is idle, it schedules null thread.
>So if  you see that  the null thread is "running" it means the
>application is now idle.
>However, the null thread internally calls $HIBER, and the applciation
>will now be  in HIB state.
>So from pthreads library perspective null thread will always be
>"running", however,  from the kernel perspective it would be
>HIBernating.
>To view the state  of the  process, you could issue a:  $ SHOW SYSTEM /
>MULTI /FULL
>This command will show what state each kernel thread is in.
>If it is  HIB, then the  process is not accumulating CPU time.
>
>-Sandeep


But it didn't answer the question.  Why are two threads which should be
idle accruing CPU time at an alarming rate?


-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

All your spirit rack abuses, come to haunt you back by day.
All your Byzantine excuses, given time, given you away.