| The watchdog isn't able to detect such hanging upon I/O situations,
unless the considered process performs busy waiting and therefore
eats CPU, which would be detected as a process looping event. Such
hanging situations as you describe may be normal (process is waiting
for another one to read the mailbox and free space for the new message
into it), or the programmer would have added the IO$M_NORSWAIT flag
to the $QIO Write operation, in order to avoid the hang. However,
it could be interesting indeed to add an event check for this into the
Agent, for given processes that could have been badly programmed.
In waiting, one could use the
SNS$EXAMPLES:SNS$CHECK_PROCESSES_STATES.COM
sample command file that will detect process stuck in odd states
(essentially MWAIT state, but possibly one of the following:
MWAIT/CEF/COM/COMO/CUR/COLPG/FPG/HIB/HIBO/LEF/LEFO/PFW/SUSP/SUSP0)
You may get some help about how to run it, using:
@SNS$EXAMPLES:SNS$CHECK_PROCESSES_STATES.COM HELP
Regards,
-- Olivier.
|
| SNS$CHECK_PROCESSES_STATES.COM seems to have a small problem. At
least on OpenVMS V7.1, f$pid(0) is not allowed. If I substitute
$ ctx=""
... f$pid(ctx)...
instead, it seems to work as intended.
_veli
P.S. Yeah, V7.1 is not supported SNS-wise.
|