Thanks Rainer,
sorry if I made myself not clear enough. It's not a problem of starting VNC,
but Xvnc. I mentioned, that I have exactly the problems of a gray screen
described in Andre Moreira's article. His solution is, to start xdm at
startup time. That's the point I cannot overcome.
Just for clarification.
I have a server without any console. So no local manual intervention is
possible (after installation time). All administration has to be done via a
remote (Windows) PC running VNC-client. Assuming the server boots again
after a power fail Xvnc should be started via inetd on the request of the
remote PC. Xvnc *is* running (ps -ax), but the VNCclient shows the mentioned
gray screen. This is the point where a running xdm is required. All attempts
to start xdm in a start-up script, e.g. /sbin/init.d/boot.local fail.
I simply don't know what to try next.
- Wilfried
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
