Adam Chlipala wrote:
> Adam Megacz wrote:
>
>> Adam Chlipala <[EMAIL PROTECTED]> writes:
>>
>>
>>> I'm still having trouble starting the domtool-slave server on mire.
>>> Running as principal "domtool/[EMAIL PROTECTED]", the daemon can't read
>>> ~domtool/keys/mire, despite the fact that "system:domtool rlidwk" shows
>>> up in the "fs la" output for that directory. Any ideas?
>>>
>>>
>> That's because there is no pts entry for "domtool.mire".
>>
>>
>
> But I thought domtool.mire was supposed to belong to group
> system:domtool. Is that not what you guys are planning?
>
> I know I could have added the mire principal directly, but I thought my
> experience was a sign that the intended set-up wasn't working.
>
Oh, and now I remember why I didn't just do this. These command-lines
all give the usual generic error message, which I interpret as
non-recognition of a principal name:
([EMAIL PROTECTED]:/afs/hcoop.net/user/d/do/domtool/keys)
fs sa mire domtool/mire read
fs sa mire domtool.mire read
fs sa mire domtool/mire.hcoop.net read
fs sa mire domtool.mire.hcoop.net read
fs: Invalid argument, possible reasons include:
-File not in AFS
-Too many users on access control list
-Tried to add non-existent user to access control list
_______________________________________________
HCoop-SysAdmin mailing list
[email protected]
http://hcoop.net/cgi-bin/mailman/listinfo/hcoop-sysadmin
