Hi
With help from past postings, I managed to get VNC running with a dtlogin on
Solaris 8 X86. I cobbled together a vncserver wrapper script with a timer loop
that detected when /tmp/.Xn-lock disappeared, added some recommended lines to
Xvnc startup and kicked the whole thing off from Xservers in /etc/dt/config -
3 vnc sessions that started at boot time and which demanded a Unix login as
well as the vnc password, which disappeared when I shut the vncviewer session
down and reappeared a few seconds later with another dtlogin prompt. Just what
I wanted.

Have recently upgraded to Solaris 10 X86, and ported the scripts across with 1
or 2 minor changes to paths, nothing very significant. vncserver 3.3.7 is
supplied on Sun "goodies" package and works a treat from command line.

When trying to run my Solaris 8 scripts, I end up with a dtlogin screen which
behaves as expected, but then the session shuts down completely after briefly
displaying a black screen. I see "AUDIT..blah..blah..connection rejected on
127.0.0.1" or suchlike in the vnc log.

The only way I have been able to get a session going is by reducing the number
of Xvnc sessions to 1, and keep trying to log in until it finally succeeds -
usually the 2nd or 3rd attempt. I have disabled the "-xauth...." line in my
vnc wrapper script as well.

This is a bit frustrating, because I'm not sure if I'm looking at a vnc
problem (unlikely), an X server config ignorance (on my part) problem or a
general change in how Solaris 10 handles the whole idea of authority with
regard to X sessions.

Any pointers, ideas or suggestions (other than "get linux") would be
appreciated.
Thanks
Tim Drake
(Quacking up under the strain)
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to