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 Is it official AFS policy that this is supposed to work this way, and will continue to work this way in the future? 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. - a _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
