VNC on HP-UX

[Mauro Forcolin]

Hello,

I'm running VNC on HP-UX, and although I can get the client to connect properly, I can't manage to get the session to start with CDE. Everytime I start I get the standard X environment, whihc does not let me do anything.

This seemed to work before the server was hardened. I checked the xstartup file (which as not been modified), and all the files/commands referenced in there are still accessable.

Any ideas,

Thanks.

[Martin Johnson]

What did you do to harden the server?

Marty

[Alex Glennie]

any clues in /home//.vnc/:1.log
for which ever user started the VNC server ?

Try killing the vncserver, restarting it and then run the vnc client .....

To confirm the problem you have - vncserver running on hpux, trying to connect via vnc client all you get is a grey mesh screen plus a set of cross-hairs / mouse pointer ?

ps is the following process running on the hpux system -> dtlogin, if not use /sbin/init.d/dtlogin.rc start

[Wodisch_1]

Hi,

the VNC server is just executing a (perl) script containing the "session" you get. And that usually consists of a "mwm" or "twm" window manager, and an "xterm" or "dtterm" windows - that's all.
If you want to have a "CDE" session, maybe even with the login-dialog first, then you'll have to start the "VNCserver" dirst (but "passive" - nothing else started in that session), and then tell your "dtlogin" to send the login-dialog to the virtual frame buffer of your VNC (i.e. something like ":1.0"). You will have to enter this in "/etc/dt/config/Xservers"...
Oh, and then your VNC server must be started BEFORE your CDE starts!

BTW, that is not what most of us do with VNC - AFAIK most of us simply like to start a window manager and a terminal window in VNC, nothing more. Since the VNC client is stateless, you VNC server has to keep all the nformation, and that would be quite a lot in case of a CDE session (but not that much for a pretty restricted "failsafe" session).

HTH,
Wodisch