[OpenAFS] Re: "group prefix doesn't match owner"
Mon, 3 May 2010 19:59:46 -0400
On Mon, May 3, 2010 at 6:42 PM, Adam Megacz <firstname.lastname@example.org> wrote:
> Derrick Brashear <email@example.com> 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. =A0Is it official AFS policy that this usage is supported?
>> Which usage? I'm not sure what you're asking.
> Sorry, let me rephrase. =A0The following sequence of commands generates a=
> 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".
> =A0$pts cu blah
> =A0$pts creategroup blah:booh -owner blah
> =A0$pts delete blah
> =A0$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
> 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
> 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). =A0Or maybe let "-force" override the error.