Nov 08, 2018 Back to Mac, in terminal, type 'xterm&'. In a X terminal, using ssh login to redhad, as Rod suggested. I can login but got two warnings: Warning: untrusted X11 forwarding setup failed: xauth key data not generated Warning: No xauth data; using fake authentication data for X11 forwarding. Although I got those warnings.
Warning No Xauth Data
Warning: untrusted X11 forwarding setup failed: xauth key data not generated
Warning: No xauth data; using fake authentication data for X11 forwarding.
[735] May 27 22:39:54 lastlog_perform_login: Couldn't stat /var/log/lastlog: No such file or directory
[735] May 27 22:39:54 lastlog_openseek: /var/log/lastlog is not a file or directory!
#!/bin/busybox sh
mount -t proc -o nosuid,noexec,nodev proc /proc >/dev/null 2>&1
mount -t sysfs -o nosuid,noexec,nodev sysfs /sys >/dev/null 2>&1
mount -t devtmpfs -o mode=0755,nosuid devtmpfs /dev >/dev/null
Here is my scenario The applications that I want to run are on Linux Server [NFS] and the client machines [CIFS] that are having problem in locking the .Xauthority files are Macs which share the same domain as that of client solaris machine. i.e. The home directory of particular user on Solaris & the home directory of that user on Mac have same contents. When I ssh -X from Solaris to the server, everything works fine, no error messages. When I ssh -X from MACs to the server, I get the following warning messages. /usr/X/bin/xauth is the path on the server. If I try to break the lock by sudo /usr/X/bin/xauth -b quit, I get the following error When I ssh -X from any my MacBookPro to the server, I have checked sshd_config on both the server and the Mac clients, there is nothing that seems wrong, but if you guys have insights then please share. --- Deleting .Xauthority files work, but thats not a good solution. I mean, everytime I have to run any X forwarding application I have to delete the .Xauthority file