[2488] in Release_Engineering
"dash" needs a file in a replicated volume not in the rel-eng cell
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Wed Nov 21 13:17:45 1990
From: paul@ATHENA.MIT.EDU
Date: Wed, 21 Nov 90 13:17:32 -0500
To: afsreq@ATHENA.MIT.EDU
Cc: rel-eng@ATHENA.MIT.EDU, cfields@ATHENA.MIT.EDU, nschmidt@ATHENA.MIT.EDU,
Hello,
Peter Roden decided some weeks ago that the "dash" program
(previously known as the Athena DeskTop or ADT) should have its menu
configuration file ("Dash.menus") in AFS so that content may be
changed outside the release cycle.
We anticipate that a minority of users will actually need to
read this configuration file when they login, but there may still be
occasions of a few hundred reads within a few minutes, and
fault-tolerance is important, hence the request for a replicated
volume. The file doesn't need to be in its own volume if an exisiting
one fits the demand.
I have basically *no* idea how AFS works beyond the design and
light maintenance level, so I can't tell you exactly what should be
set up. I can give you these contraints:
- must not be down without warning often
- must be writeable by a few people (paul, cfields, lavin) and
readable by system:anyuser
- will be read at login by any user who creates ~/.dashrc
- is one small file under 50K
- will be linked to by /usr/athena/lib/Dash.menus
I should have asked for this long ago but was completely
unsure of what the needs and constraints were. If there are any
questions about specifics, please see Craig Fields while I am out of
town.
So, could someone please find or create us a replicated volume
into which we can put the Dash.menus file? I apologize for having
become the sort of person who used to drive me nuts by asking for
something late and then going on vacation :(.
-Paul
