Port.status shows what is currently running on that PID
Not what was running when the lock was set.

The "process" is not the "program".  You are using the words interchangebly 
when they are not.
A process can run a long stack up and down adding and pruning.  The call stack 
only shows the current stack of the stack, not what the state was when the lock 
was set.

If a member of the old call stack had set a lock, that lock persists until the 
entire call stack is completely depleted.
Which could be 20 routines later.

-----Original Message-----
From: Jeff Schasny <jscha...@gmail.com>
To: U2 Users List <u2-users@listserver.u2ug.org>
Sent: Thu, Sep 8, 2011 11:30 am
Subject: Re: [U2] Lock Status

I disagree.
If I run LIST.READU and note the PID of a process holding a lock on an 
tem then run PORT.STATUS on that PID the only way that the program 
hown by PORT.STATUS as currently running is not the process holding the 
ock would be if the program ended (thus dropping the lock) before I ran 
Wjhonson wrote:
 That's not the case.
 PORT.STATUS shows you what that PID is currently doing when you run it.
 Not what it was doing an hour ago for example.
 Not what it was doing when it set the lock.
 Just what it's doing now.
 In Unix/Universe world.

 If you are so lucky to know about the lock *right when* it's being set, then 
ou are right.
 But in my experience that is a very rare occurence.
 And in this particular example, he already stated that it was a lock left set 
ome time earlier.
 You can only know the program being run by that PID if that program is in some 
ort of waiting condition and had been waiting since it set the lock.

U2-Users mailing list

Reply via email to