Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!CIVILGATE.CE.UIUC.EDU!lray
From: lray@CIVILGATE.CE.UIUC.EDU (Leland Ray)
Newsgroups: comp.sys.apollo
Subject: Node 0 locking a directory
Message-ID: <8912062018.AA09605@civilgate.ce.uiuc.edu>
Date: 6 Dec 89 20:18:11 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 22


Ahh, the infamous node 0 lock.

The short answer: get rid of the lock using /com/ulkob. It will do it
regardless of the node ID locking the object.

The long answer: say a user has locked a file called /meat/steak. Then
the user decides to change the name of the directory from /meat to /food.
So, the user, while locking steak, changes the directory using chn (or mv).
The next time he tries to create a file in /food, he will be very depressed,
for the node will appear to hang for a while and do nothing.

Well, if you view the lock table from the offending machine, you will see
a directory locked by node 0.

This used to happen all the time at SR9. I just tried it at SR10 and it no
longer happens, so I would wager that this is fixed.

Just spendin' my days,                  Leland Ray
                                        Systems Administrator
  Soakin' in them cathode rays.         UIUC - Dept. Civil Engineering
                                        (217) 333-3821