On Wednesday June 11, tobi@xxxxxxxxxx wrote: > Experts, > > I have a strange problem on a diskless client. At ramdom intervals > (hours) when I try to open an xterm I get the message > > > xterm > No protocol specified > xterm Xt error: Can't open display: :13.0 > > Doing an strace on xterm I find that it gets a 'stale nfs handle' > when trying to open .Xauthority. > > If I do a > > cat .Xauthority >/dev/null > > things go back to normal and I can open xterms again ... > > so how can it be, that xterm gets a stale nfs handle error while > cat can read the file just fine and after cat did it it works for > xterm as well ? xterm is setuid root. cat is not. The filesystem is exported in a way the causes 'root' accesses to be treated as accessed by 'nobody'. If the NFS server is Linux, then the export option "no_root_squash" can fix this. If the .Xauthority file is in cache on the client, xterm will be able to read it with no problem. If not, it will send a request to the server for root to be able to read the file, and the server will reject the request. It should really return EACCES rather than ESTALE though ... what is the NFS server? NeilBrown -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
