[5952] in Athena Bugs
attach and hesiod domains
daemon@ATHENA.MIT.EDU (Ken Raeburn)
Wed Sep 5 18:35:20 1990
Date: Wed, 5 Sep 90 18:35:03 -0400
From: Ken Raeburn <Raeburn@MIT.Edu>
To: bugs@ATHENA.MIT.EDU
User 1, who's primarily interested in stuff in the "watch" realm -- file
systems and such:
[multics] {~}
<48 6:02pm> % setenv HES_DOMAIN watch.mit.edu
... wants to look at Marc's homedir ...
[multics] {~}
<50 6:18pm> % attach -n marc
attach: filesystem marc (beeblebrox.MIT.EDU:/site/u/marc) mounted on /mit/marc.watch (read-write)
Now, user 2 on the same host (I unset HES_DOMAIN at this point) decides he
also wants to look at Marc's homedir (which of course should have a
different meaning -- consider attaching rfrench@stanford.edu if that makes
the distinction more clear):
[multics] {~}
<53 6:18pm> % attach -n marc
attach: Filesystem "marc" is already attached
[multics] {~}
<55 6:18pm> % attach | grep marc
marc /mit/marc.watch raeburn w
This example is rather contrived, but demonstrates the point. I suspect
confusion would arise also from person 1 attaching "marc@athena.mit.edu"
and person 2 attaching "marc" -- with the information currently stored, it
probably should not recognize that the two are the same. (I haven't tried
it, but with the problems of having two file systems with the same mount
point, I don't think it would be very enlightening in any case.)
The attachtab file only lists the domain when it is explicitly specified.
It should contain it always (or have some way of recognizing when the
domain of the hesiod information is different from the default domain of
the machine, though the former is probably preferable for all purposes but
readability), and probably display it only when (or exactly when) it
differs from the default for the user (or when requested via command-line
options?).
