Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ucbvax!RICHTER.MIT.EDU!krowitz
From: krowitz@RICHTER.MIT.EDU (David Krowitz)
Newsgroups: comp.sys.apollo
Subject: Re:  uwm/xownsroot login hangs on diskless noes
Message-ID: <9101241626.AA24781@richter.mit.edu>
Date: 24 Jan 91 16:26:56 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 29

An oberservation that may help you ...

The /tmp directory is actually a link to `node_data/tmp on Domain/OS systems.
For machines with their own boot disk, this translates into the directory
//my_disk/sys/node_data. For diskless machines, this translates into the
//my_partners_disk/sys/node_data.my_node_id/tmp directory (sigh, I missed
the "/tmp" on the end of the first example ...). The default file protection
for files created in /tmp is taken from the ACL of the /sys/node_data/tmp
directory for machines with disks and from the /sys/node_data.my_node_id/tmp
directory for machines without disks. The ACLs for the /sys/node_data 
directory (and it's subdirectories) should have been setup when the OS was
installed; but the ACL's for the /sys/node_data.my_node_id directory used
by the diskless machines are set up when the diskless machine is first booted
off of the partner according to the /sys/net/netman.rc shell script. This is
usually a link to either netman.bin_sh or netman.com_sh, which results in the
diskless node's /tmp directory receiving either Unix-style or Aegis style
ACL's when the diskless node is first booted. My guess is that the ACL's
on you /sys/node_data/tmp directory are different from those on your
/sys/node_data.my_node_id/tmp directory, and that the culprit is the
/sys/net/netman.rc file either being linked to the wrong environment, or
simply having the wrong file protections being set by the file.


 -- David Krowitz

krowitz@richter.mit.edu   (18.83.0.109)
krowitz%richter.mit.edu@eddie.mit.edu
krowitz%richter.mit.edu@mitvma.bitnet
(in order of decreasing preference)