Back when cclausen was an admin, he was close to flying into a rage because we used an AFS layout that included on users' home volumes subdirectories that they didn't have write access to. He said that "the AFS way" was to create volumes freely because they are cheap and helpful for organization.
Now megacz has been making recommendations which seem to be based on viewing volume creation and/or maintenance as a significant cost, recommending log files be stored in special directories of users' home volumes rather than separate volumes. I'm a complete AFS administration neophyte, so I've been accepting as gospel anything that anyone with an "expert" hat says. Even though cclausen proved unreliable in some important ways, I've continued to take his views on volumes as the received wisdom, since he didn't indicate that they were controversial. I have a feeling docelic is in a similar boat. I'm not trying to accuse anyone of being wrong here. I'm just hoping to come up with a single set of guiding principles for AFS design that we can all agree to follow. megacz, can you explain why you don't think free creation of volumes for separate "access control domains" is a good idea, and perhaps comment on why cclausen might have had a different viewpoint? P.S.: I think this adduser/dbtool/logs stuff is the last obstacle in the way of being able to start migrating test users effectively, so it would be good to get this all resolved soon. However, it's pointless to ignore social obstacles in the way of effective administration, so I also hope we take the time to get that all figured out and get back to amiable interaction ASAP. :-) _______________________________________________ HCoop-SysAdmin mailing list [email protected] http://hcoop.net/cgi-bin/mailman/listinfo/hcoop-sysadmin
