[19] in Layered Athena
Layer doc comments
daemon@ATHENA.MIT.EDU (Richard Basch)
Thu Apr 8 11:31:28 1993
Date: Thu, 8 Apr 1993 11:31:10 -0400
To: mar@MIT.EDU
Cc: layered-athena@MIT.EDU
From: "Richard Basch" <basch@MIT.EDU>
The Kerberos configuration files are now:
/etc/athena/srvtab
/etc/athena/krb.conf
/etc/athena/krb.realms
In addition to /etc/named.boot, we also need another named configuration
file (named.mit & named.root, but these could be combined).
Do we want to use /etc/X or /etc/athena/X, given that we are otherwise
separating things?
For Kerboers, I actually recommend that the order be:
1. Environment variable (KRBCONF/ATHENACONF/whatever)
2. /etc/athena
3. /etc
The environment variable should not be used if the effective uid is not
equal to the real uid for security reasons. The reason that I recommend
that the environment variable be checked first is that sometimes there
are alternate realms that people may wish to use but are not yet in our
krb.conf file.
Here is a thought in case we wish to allow people to copy the help
documentation local. Rather than considering subsets of having a
configuration portion and a binary portion, also consider them to have a
documentation portion. Under AIX, there are 3 parts to every subset:
root, usr, and share. The "share" component would have things such as
terminfo libs, documentation, and other extensible databases.
I suggest strongly against using hard-coded names for the Zephyr servers
as it sounds like you are pre-determining how many are in use. We have
enough of a problem with load balancing and I don't think we can afford
having more than a few machines that use only a subset of the Zephyr
servers rather than spreading themselves evenly amongst all the
available ones.
One thing that is not discussed is the notification. For instance, will
a message be sent to the owner if the machine takes an auto-update?
What is the frequency that the owner will receive new release reminders?
I know these are subject to change.
-Richard
