Tony D'Amato wrote: > Okay, I'm beating my head against the wall on this one... I've compiled, > installed, and attempting to set up OpenAFS 1.4.8 as a server on Solaris > 10 x86 (originally Update 5, with some U6 patches). I'm using Sun Studio > 12 to compile the software. After setting up the services with -noauth, > using asetkey to add the afs principal, created the admin principal > 'cell_admin' (we're a former DCE/DFS shop), but when I issue the setacl > on the /afs mount point, I get the infamous error message in the > subject. Please note that due to local requirements, the Kerberos domain > is not and cannot be the same as the AFS cell name... perhaps that's my > problem?
If the cache manager, afsd, is started using -dynroot /afs does not point to a real root.afs volume. So you can't set an ACL on it. Due to the fact that the kernel module cannot start if the root.afs volume cannot be accessed when -dynroot is off, -dynroot is becoming the default on more platforms. Perhaps that is your problem. What does fs examine /afs report?
smime.p7s
Description: S/MIME Cryptographic Signature
