Hi, On Mon, Dec 19, 2005 at 04:19:01PM -0500, Jeffrey Altman wrote: > Lars Schimmer wrote: > > Hi! > > > > Today I had a strange problem. > > 1.4 server, 1.4 clients on win and linux. > > A user could went down a path to a directory and there were just 0 byte > > files in it. > > a directory listing with 0 byte files is a side-effect of not being able > to obtain stat data either because the user does not have appropriate > tokens or because all servers registered for that volume are marked as > being down. Use the "tokens" and "fs checkservers" commands on the
I was curious and tried to reproduce this situation. I found a strange (-> inconsistent) bahoviour of the (linux-)openafs-client. This is what I did: [EMAIL PROTECTED]> mkdir test;cd test;fs sa -clear joe .;echo test > test [EMAIL PROTECTED]> cd test;ls -la total 12 drwxrwxr-x 2 daemon root 2048 2005-12-20 11:00 "."/ drwxr-xr-x 97 root users 10240 2005-12-20 10:57 ".."/ ?--------- ? ? ? ? ? "test" And here is what I didn't expect: [EMAIL PROTECTED]> cd test;ls -la total 15 drwxrwxr-x 2 daemon root 2048 Dec 20 11:00 "."/ drwxr-xr-x 97 root users 10240 Dec 20 10:57 ".."/ -rw-r--r-- 1 daemon root 5 Dec 20 10:52 "test" My guess: The openafs-client doesn't seem to enforce the r-permission correctly when the stat-data of the examined file is cached. Is this wrong, wanted or unavoidable behaviour? Regards, Frank _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
