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 ? Our home directories are automounted via nfs and then from there bindmounted into /home if that rings a bell ... cheers tobi -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten http://it.oetiker.ch tobi@xxxxxxxxxx ++41 62 213 9902 -- 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
