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

[VAXman- at SendSpamHere.ORG]

In article <b8fde033-da04-46dc-b92d-d8a472424ff1 at n18g2000vbq.googlegroups.com>, San <rsandeep80 at gmail.com> writes:
>On Feb 10, 10:47=A0pm, VAXman-  @SendSpamHere.ORG wrote:
>> [...snip...]
>
>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.

Well, I beg to differ.  This has been running since yesterday.  The threads
that *I* created have never done anything in terms of work.  There are two
internal threads (I believe these were shown in the SDA> PTHREAD THREAD -AF 
output as -2 and -4) accruing time.  The ovveral process is ticking away at
the CPU using this SDA command view as well as $ SHOW SYSTEM /MULTI /FULL

2180068A *************** HIB     12      79   0 00:06:26.07      287    341 M

2180068A *************** HIB     12      79   0 00:06:27.39      287    341 M
 

I'm not interested in the theoretical when the reality is before me. ;)
-- 
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.