[14707] in Athena Bugs
Re: several bugs with the new release
daemon@ATHENA.MIT.EDU (bdrosen@MIT.EDU)
Fri Sep 27 09:53:27 1996
From: bdrosen@MIT.EDU
To: Jonathon Weiss <jweiss@MIT.EDU>
Cc: bugs@MIT.EDU
In-Reply-To: "[14698] in Athena Bugs"
Date: Fri, 27 Sep 1996 09:53:23 EDT
|> On an sgi setup for remote access, when someone logs off on the cons
*ole
|> the reactivate script is run. This detaches all the lockers. This causes
|> problems for users logged on remotely as this will cause renew to fail
|> to get new tokens for remote users. (this may be true on the suns as well
*)
|>
|> Note that there is not yet a supported methid for doing for making an
|> SGI remotely accessable, so I can only guess at what is going on.
|> Does the SGI in question have PUBLIC=false in /etc/athena/rc.conf.
|> That should prevent the problem you describe.
|>
The machine on which this was reported was dorian (an e40 machine
I believe).
Looking over the reactivate script, it appears that PUBLIC
being false should not affect this problem .
1 If reactivate is called with -prelogin with PUBLIC false the script
exits.
2 If reactivate is called with -prelogin with PUBLIC true the script
does not detach the lockers.
3 If reactivate is not called with -prelogin, then the value of PUBLIC
does not effect whether lockers are detached.
Also, by default dflags should be -clean which *should* cause detach
to not detach all the filesystems.
(this is from /afs/athena.mit.edu/system/sgi_53/srvd.80/etc/athena/reactivate)
Brett Rosen
