----- Original Message ----- From: "Marc Mazas" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, August 30, 2002 12:12 PM Subject: TR : Display number with inetd
[snip] > 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 ... > > Marc > If your goal is to always be sure a VNC stays running then you should be able to do this with a shell script. I haven't tried it, but what comes to mind is run the vncserver command with the hardcoded display "vncserver :2" in a cron job every 5 minutes or so. You could keep track of it by doing something like I saw on the Redhat Valhalla list here: https://listman.redhat.com/pipermail/valhalla-list/2002-August/014560.html Also out of curiosity, have you had trouble with Xvnc terminated? Usually start one session and have it running continuously and I can say that I've had over 100 days of uptime without VNC causing problems. -- William Hooper Give a man a match, you keep him warm for an evening. Light him on fire, he's warm for the rest of his life. _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
