[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:	DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:	See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:	STAR::VATNE

Created:	Mon Oct 30 1989
Last Modified:	Mon Dec 31 1990
Last Successful Update:	Fri Jun 06 1997
Number of topics:	3726
Total number of notes:	19516

1810.0. "Does DECwindows put an exclusive write lock on SYSUAF?" by RHETT::GILBERT (Jeff Gilbert, VMS workstations support, CSC/AT) Wed Nov 29 1989 10:56

I have a customer who wants to know if DECwindows puts an exclusive write
lock on SYSUAF.DAT during login, session pause, or session exit.

It seems a workstation hangs (once a week) after pause ... and it
hangs because it is waiting on the lock to sysuaf.dat.  Customer
could not tell me if another process had the file lock or not.
Customer was at DECUS last week and someone told him this is a known problem.
The only way to get the sysuaf.dat file unlock is crash the
workstation that is hung.

	Thanks,
	Jeff

T.R	Title	User	Personal Name	Date	Lines
1810.1	Some ideas...	MOVIES::GROSSMITH	Mike - VMS Devo/Europe	`Thu Nov 30 1989 03:07`	13
	Surely it can't take out such a lock during session pause, otherwise, in a cluster, no other process would be able to get to the UAF if any W/S was paused. Clearly this can't be the case. I haven't looked at the code, but I would imagine that LOGINOUT.EXE works the same way, (as far as the UAF is concerned), in a DECwindows or non-DEcwindows environment. Anyway, you can peruse the lock database with SDA, perhaps that will help you determine which process has the lock. /Mike
1810.2		LESLIE::LESLIE	Andy �� Leslie VMS/CSSE Newbury	`Thu Nov 30 1989 23:47`	4
	SHOW DEV/FILES might be a little more straightforward... - Andy �� Leslie