> -----Original Message----- > From: Marc Mazas [mailto:[EMAIL PROTECTED]] > > If I understand correctly your answers, the -inetd argument of Xvnc > causes this one to always ignore the :XX display number argument but > find the next available one. I can understand the rationale, > since this is intended to serve many users. > > But I think it would be much better that Xvnc tries to use the given > display number and only if in use find the next available > one. Wouldn't this be an enhancement ?
I read the :xx display number option to Xvnc as the default ofset from the ports 5800, 5900 and 6000 for the webserver, rfbcommunication and X11 communication. Have you tried to force the use of these ports with the '-httpport', '-rfbport' or '-port'? (I'm not sure if the '-port' option is for X11 communication, it's just I cannot think of any other use related to Xvnc) Maybe, the '-pn' or '-nopn' options can do something for you, I still have not figured out what they realy do, it's only I have to use '-pn' on HP-UX. > > In my case, the display number is a fixed configuration > parameter of the > Apache Jserv server, and there is only one X client for all the server > (I assume a servlet), not one X client for each real user. I had the > idea to use inetd in order to have it relaunch the vnc server in case > Xvnc terminated for any reason, and thus to hope the application will > continue to work. So I would have to use the :2 display number, but I > cannot guarantee it will always be this one ... A $DISPLAY value of :2 indicates the use of port 6002 for X11 communication. Try using '-port 6002' (note, I'm not sure if -port indicates this usage...) Then, a work-around can be a fixed `vncserver :2` session which always runs. (might also include the -localhost option) and use an other vnc-session to view the fixed session with `vncviewer localhost:2`. CBee _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
