[533] in Moira
A couple of things
daemon@ATHENA.MIT.EDU (Mark Rosenstein)
Tue Jan 5 17:42:57 1993
Date: Tue, 5 Jan 93 17:42:41 -0500
From: Mark Rosenstein <mar@MIT.EDU>
To: pjb@Athena.MIT.EDU
Cc: bug-moira@Athena.MIT.EDU, accounts@Athena.MIT.EDU
In-Reply-To: Pamela J. Benson's message of Tue, 05 Jan 93 15:58:48 EST <9301052058.AA17621@pickle-pebble>
The first part of this is easy. 17.nazli doesn't have, and apparently
never has had, a quota assigned to it. So you can't see what it is
now because there isn't one. Similarly you can't change it. But you
can add a new quota for the filesystem. And since it is an AFS
filesystem, the quota is of type ANY, not USER.
The field labeled "update fileserver" in the displayed information
about a filesystem is the field that's asked about as "Automatically
create on fileserver" or "Propagate changes to fileserver" in the
client programs. If this is true (or on), when you change information
about a filesystem such as type from AFS to ERR or the name, it will
attempt to make the corresponding change in AFS as well. If this flag
is false (or off), it will change the moira database, and hesiod will
reflect the change, but it won't touch the fileserver.
The filesystem "starman" didn't reactivate because I did something
stupid yesterday such that no hesiod update ran last night. I ran a
hesiod update around 1:30 yesterday afternoon, but we didn't get one
last night. Everything should run fine tonight.
-Mark
