On Mon, May 3, 2010 at 6:42 PM, Adam Megacz <[email protected]> wrote: > > Derrick Brashear <[email protected]> writes: >>>> When creating a group foo:bar as admin, I often find that I have to >>>> use the -owner parameter to see the owner to foo(something). >>> >>> I see. Is it official AFS policy that this usage is supported? >> >> Which usage? I'm not sure what you're asking. > > Sorry, let me rephrase. The following sequence of commands generates an > error, but appears to work -- by which I mean that it leaves me in a > state where there is a group named "blah:booh" but no user named "blah". > > $pts cu blah > $pts creategroup blah:booh -owner blah > $pts delete blah > $pts ex blah:booh
if it works, it generates a warning, not an error. you mean invoking a single diret command generates an error, and the above sequence does not. correct? > Is it official AFS policy that this is supposed to work this way, and > will continue to work this way in the future? uh. i don't think there's an official AFS policy, period. if the ptserver starts garbage-collecting orphaned groups, it will be documented. > If so, perhaps we should consider changing the error "Badly formed name > (group prefix doesn't match owner)" into a warning if it's being invoked > by system:administrators (who could just use the sequence of commands > above instead). Or maybe let "-force" override the error. _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
