[1403] in SIPB-AFS-requests
Re: Reorganizing AFS machine configuration directories
daemon@ATHENA.MIT.EDU (yandros@MIT.EDU)
Sun Jun 5 02:25:38 1994
From: yandros@MIT.EDU
Date: Sun, 5 Jun 94 02:25:12 EDT
To: ghudson@MIT.EDU
Cc: star-maintainers@MIT.EDU, webmaster@MIT.EDU
In-Reply-To: "[834] in Charon_Maintainers_Archive"
Note for the public: star-maintainers goes to a public discuss
meeting. Just FYI.
e.g. the http-bogon script in foo-server/common should probably be in
project.www.
http-bogon[.c] isn't a script; it's too simple to be a script. :-)
(you did ask for comments. :-)
There are a number of other things involved when considering the
separation of services and servers.
o namespace collision. One of the more important things to come out
of the server reorg is the centralized discuss service.
/afs/sipb/project/discuss is obviously something different. I'd
suggest another layer, either below /afs/sipb/project or above
(/afs/sipb/service?). Looking around, I notice /afs/sipb/system,
which currently has two directories:
cap: last mod time: may 10, 1990. Contains vax and RT binaries.
xdm: last mod time: september 4, 1989. Contains mostly symlinks
to /srvd/etc/athena/xdm (which doesn't exist) and an xdm
config file to old to have a version number included.
I believe it's probably safe to assume that this isn't used much
anymore. :-) This new level could include servers and/or services
and/or machine configuration (/afs/sipb/project/office-machines is,
um, a little bit messy. (for example,
...office-machines/cutter-john, containing some notes from when
cutter ran AIX 1.2.1 and the mini athena port.
o where do you keep the kernel? the kernel config file? The list of
kvars that need to be run on the kernel? These are very much server
things, but they're usually part of the service (for example, when I
did the kernels for enterpoop and senator-bedfellow (way back when),
I tagged them `NEWS-SRV', since that's what they were.
o common: do we really need this at all? With 7 servers, it's
unlikely that much will be common to all, so you'd have to further
subdivide. As much as common/afs appeals to my sense of irony, I
think it'd be much better to just use `afs'.
o copying from AFS into local disk: sure, it's technically not a
problem, but practically it is. People don't do it. They forget,
or they don't know, or they're just tired. In the process of
creating mkserv scripts for our servers (which we should do, by the
way. :-) we'll have to make .sync files; whlie doing this it should
be easy (or at least not too hard) to make synctree scripts for the
local files. I'd suggest perhaps 3 or 4 times a day, but I think
the synctree would be inexpensive if written well; that could easily
be wrong. Jonathon, Matt, Matt, Barbara, and bert all have lots of
experience writing mkserv scripts.
chad
