We see that from time to time. However, only when we issue LIST.READU EVERY. It is a deadlock. You have to find out who the two users are. In your example, it looks like a phantom or batch process and a user on a terminal. You have to pick one of the two to kill in order to free up the lock. We usually LOGTO UV. Go into deadlock administration and take care of the situation that way. Anthony
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Hennessey, Mark F. > Sent: Monday, December 19, 2005 12:31 PM > To: [email protected] > Subject: [U2] UV: LIST.READU question > > > We've come across some output from LIST.READU that appears to > not be documented. After the usual (and documented :) Group > and record locks, we saw: > > 0037: Active File Waiters: Owner Waiter > 0038: Device.... Inode.... Userno Userno > 0039: 22595385 493 44841 13 > > So, it appears to me that user 13 was waiting for user 44841 > to get done with whatever file has inode 493. > > Has anyone seen this before, and have an idea of what > qualifies a "Active File Waiter" to be captured by LIST.READU? > > We're running UV 10.0.8 on Solaris 8, by the way. > > Mark Hennessey > State of Connecticut > DSS/MIS Child Support Systems > Voice: 860-424-5261 > Fax: 860-424-4956 > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
