> Make sure your openafs kernel module and openafs-client package are > both upgraded to 1.4.2-2
one of the things i noticed, in our kerberos database there is a principal afs@<kerberos-realm> but no principal afs/<domain>@<kerberos-realm>. also, the aklog produces different log entries on the krb5kdc: aklog from sarge - afs@<kerberos-realm> aklog from unstable - afs/<domain>@<kerberos-realm> after upgrade to 1.4.2-2 the afslog and aklog succeed but /afs is not accessible after aklog (works with afslog)... vlad
pgpcY9gVpIZyf.pgp
Description: PGP signature