[25] in Release_7.7_team
Moira client
daemon@ATHENA.MIT.EDU (Richard Basch)
Mon Mar 14 19:34:10 1994
Date: Mon, 14 Mar 1994 19:33:33 -0500
To: release-77@MIT.EDU
From: "Richard Basch" <basch@MIT.EDU>
a) Pull the moira client from the packs so that it can be changed
between releases. (ie, put it in a locker)
User Visibility: High (listmaint, mailmaint)
Effort: Low
Knowledge: No one in particular
Hits: Documentation, OLC
Misc. This would be easy to do and does not take any particular
expertise. The only issue that I can think of is, if we
do this, do we put an attach & run script in its place,
or just depend on user education?
The user visibility can be low... if we treat "moira" like "pts", and we
symlink it to a central repository in AFS, then the program is
essentially in the release, but not updated in the release cycle... it
is updated when it needs to be. Normally, I wouldn't suggest this, but
since this is one of the core services that Athena provides, and since
listmaint, and other Moira utilities are commonly used, it might make
sense to do this.
In essence, the procedure might be:
/usr/athena/bin/blanche -> /afs/athena.mit.edu/system/$bindir/blanche
/usr/athena/bin/moira -> /afs/athena.mit.edu/system/$bindir/moira
/usr/athena/bin/listmaint -> /afs/athena.mit.edu/system/$bindir/listmaint
/usr/athena/bin/mailmaint -> /afs/athena.mit.edu/system/$bindir/mailmaint
. . .
Effort: easy
Impact: minimal
-Richard
