On Fri, 25 Oct 2002 [EMAIL PROTECTED] wrote: > >>>>> "Derrick" == Derrick J Brashear <[EMAIL PROTECTED]> writes: > > On Thu, 24 Oct 2002 [EMAIL PROTECTED] wrote: > >> Since we use our own homegrown architecture for distributing changes > >> to these volumes, and the updates are exclusively performed via vos > >> restore, the option you are proposing would help us close a small hole > >> that has bothered me for year -- namely, rogue users (the ones that > >> think they understand the AFS volume structure well enough to do this) > >> will sometimes hack a RW volume and then perform a manual vos release, > >> bypassing the supported up[date mechanism. > > Derrick> What he's proposing shouldn't help you, IIRC. That's a volserver change > Derrick> you want, and he's proposing fileserver changes. A change in the fssync > Derrick> interface might be able to be made to do what you want... > > Why do I need a volserver change for this? I just want to make it > impossible to write to the RW volume via the cache manager. Its the > rogue "fs mkmount", followed by manual hacking that I want to ban.
Oh, as opposed to the manual release. Fine. -D _______________________________________________ OpenAFS-devel mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-devel
