[146] in SIPB-AFS-requests
aklog in /afs/sipb
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Sat Jan 13 13:34:34 1990
From: qjb@ATHENA.MIT.EDU
Date: Sat, 13 Jan 90 13:34:40 -0500
To: sipb-afsreq@ATHENA.MIT.EDU, vice-squad@ATHENA.MIT.EDU,
Right now, there are copies of aklog in serveral places:
/afs/athena.mit.edu/service/@sys/aklog
/afs/testers.athena.mit.edu/service/@sys/aklog
/afs/sipb.mit.edu/service/@sys/aklog
/afs/athena.mit.edu/system/afsuser/@sys/aklog
I suggest that we do something about this. /afs/athena/service
is replicated on all the servers in the athena cell except for
circe, so it seems like a good candidate for being the survivor.
I guess it's okay to have lots of copies, but I get a little
worried about how we are going to keep them all up to date. I
think the one in afsuser could be a symbolic link to the one in
service and that it is not necessary to have copies in the other
cells since athena workstations are in the athena cell unless
their maintainers have changed the configuration. In those
cases, perhaps aklog should be local anyway. Another reason for
keeping the one in service is because that is the one that
attach uses by default (/etc/attach.conf). (Actaully, attach
uses /afs/athena/service/aklog.) Besides, it was put in service
to begin with because we thought that that was the right place
for it considering that it is needed by anyone from anywhere who
wants to authenticate to the athena afs cell.....
Comments? This comes up because of thinking about the number of
copies of aklog that will need to be updated if we change it.
Jay
