> > I've noticed that the X11R6 I compiled for my Sparc running NetBSD-1.1
> > has some problems with .Xauthority. Very often it doesn't seem to be able
> > to read it, for no reason. Using xauth to read it works, and right after using
> > xauth, the problem disappears (for some time):
> 
> Your .Xauthority is not world-readable, and xterm is dumb enough to try and
> read it with its setuid-bit in effect. This will (usually) fail on a NFS
> mounted filesystem. Unless all of the file bits are in the local machine's
> cache, in which case there won't be a NFS read call to the server. Note that,
> on NFS filesystems, it is the read call (not open(2)) that returns
> "Permission denied" (esp. for processes running as root).

But then, why does xterm work correctly later ?


	Stefan

PS: and I'm not supposed to have the .Xauthority world-readable. That would
    kind of defeat the purpose.
PPS: by the way, the +ut option doesn't seem to have any effect on xterm:
     it never adds itself to the utmp file.
PPPS: Why should xconsole and xterm be setuid ? if /dev/console belongs to
      user X, then user X should be able to redirect its content to xconsole
      without going through root.