I was mislead by the .Xau... it is not X but gdm that actual controls this. and there is a gdm config file (with plenty of comments) that does the job.
# Better leave this blank and HOME will be used. You can use syntax ~/ below
# to indicate home directory of the user. You can also set this to something
# like /tmp if you don't want the authorizations to be in home directories.
# This is useful if you have NFS mounted home directories. Note that if this
# is the home directory the UserAuthFBDir will still be used in case the home
# directory is NFS, see security/NeverPlaceCookiesOnNFS to override this behaviour.
UserAuthDir=/tmp
and all is well.
Peter
s. keeling wrote:
Incoming from Pete:
What is the purpose of the var XAUTHORITY?
(0) keeling /home/keeling_ echo $XAUTHORITY /home/keeling/.Xauthority
And is there a known way to put that .Xauthority file NOT in /home/user ?
$ xauth list # if you already have keys, skip next $ xauth generate . # perform if you have no auth file $ xauth nextract keeling.xa $DISPLAY # should be the only step needed.
Switch to client machine.
$ export DISPLAY=$HOSTIP:0.0 # $HOSTIP == remote IP address/`hostname -f` $ xauth nmerge $HOSTIP:~keeling/keeling.xa
_______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
