Further developments. I decided to bypass the firewall issues for the moment, drop the firewall, and go on to filesystem setup.
As I write this, I am logged in as root, and have the kerberos tickets and aklog tokens of user zzz, who is the admin for the AFS server. And omega:~# pgrep -fl afsd 3708 /usr/sbin/afsd -stat 2000 -dcache 800 -daemons 3 -volumes 70 -fakestat -afsdb 3712 afsd omega:~# tokens Tokens held by the Cache Manager: User's (AFS ID 2) tokens for [EMAIL PROTECTED] [Expires Aug 13 01:18] --End of list-- omega:~# fs setacl /afs system:anyuser rl fs: You don't have the required access rights on '/afs' Yet again. Out of sheer frustration, omega:~# cd /etc/openafs/server omega:/etc/openafs/server# ln -s /etc/krb.conf . omega:/etc/openafs/server# fs setacl /afs system:anyuser rl fs: You don't have the required access rights on '/afs' Any ideas on what might be going on ? The client is definitely up as the grep above shows. And I did not start bosserver -noauth. One possible lead : /etc/openafs/afs.conf.client : AFS_CLIENT=true AFS_AFSDB=true AFS_CRYPT=true AFS_DYNROOT=false AFS_FAKESTAT=true Note the dynroot setting above. Could that be causing this ? From /etc/openafs/afs.conf : ENABLE_AFSDB=on ENABLE_DYNROOT=off I intend to have both server and client running on this machine. _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
