From: Frank B. <fb...@sy...> - 2005-08-30 19:56:51
|
What James tried to tell you is that there are two ways to start the vnc server. One is the way you did it - using xinted - which results in the behaviour you dislike. To get the behaviour you want, you should start the server using "vncserver" command instead (what James called the "normal" way). http://www.realvnc.com/products/free/4.1/man/vncserver.html Frank At 02:09 PM 8/30/05, Charles A. Monteiro wrote: >James: > >I followed a "how to" directions found at linuxreviews.org to set things >up which used xinetd, the service specs are contained in a file labelled >'xvncserver' found in the xinetd.d directory. In the file I included only >one spec > >service vnc-1024x768x24 > { > protocol = tcp > socket_type = stream > wait = no > user = nobody > server = /usr/bin/Xvnc > server_args = -inetd -query localhost -once -geometry 1024x768 -depth >24 > } > >I guess with xinetd the approach allows one to setup multiple vnc server >instances ? (I am new to all of this) i.e. a vncserver per every ip >service spec, the associated ip found in etc/services. > >I gather from your email that every server is meant to stay alive and and >have an associated display number i.e. that is what "normal" is. > >I can already spawn multiple connections which work fine but I can't get >to a pre-existing one i.e. they seem to die. I hate to have to start all >over. > >Is it that in the above spec I have the wrong server i.e. the line above >should read: > > server = /usr/bin/vncserver > >and for server args: > > server_args = -inetd -query localhost -once :1 -geometry > 1024x768 -depth >24 > >perhaps > wait = yes > >Or is it a bad idea to run vnc on xinetd in the first place? > >thank you very much for your time, > >-Charles > > > >On Tue, 30 Aug 2005 12:55:37 -0400, James Weatherall <jn...@re...> >wrote: > >>Charles, >> >>VNC Server for Unix is normally started by running "vncserver" and will >>then >>continue to exist until you explicitly kill it with "vncserver -kill". >>The >>"vncserver" command allocates a new display number to the server, which >>is >>then used to access it from the VNC viewer. This is the "normal" way to >>run >>VNC X desktops, and does exactly what you seem to want. Please see the >>documentation (http://www.realvnc.com/products/free/4.1) for further >>information. >> >>Regards, >> >>Wez @ RealVNC Ltd. >> >> >>>-----Original Message----- >>>From: vnc...@li... >>>[mailto:vnc...@li...] On Behalf >>>Of Charles A. Monteiro >>>Sent: 30 August 2005 16:25 >>>To: vnc...@li... >>>Subject: How do I configure for remote control? >>> >>>Hi. First thanks Simon et al for the help on configuring TightVNC on >>>Linux. I am now up and running. My hopefully last issue, is >>>that I seem to >>>have myself configured to spawn new desktop sessions which >>>will exit when >>>I exit the vnc viewer. What I want to do is to spawn a new >>>session , start >>>an app in said desktop and allow for the app to continue >>>running even >>>though I exit the vnc viewer, then at a latter time I would like to >>>reconnect to the same desktop session and find the same app >>>as I had left >>>it running. >>> >>>Also there are collaborative and customer support like >>>scenarios which are >>>in the horizon and therefore I would require to be able to >>>configure for >>>"remote control". >>> >>>I thought that if I connected with a connection string like so: >>> >>>xxx.xxx.xxx.xxx:72:2 >>> >>>I would be able to connecto to a specific desktop but I think >>>part of the >>>problem is that the remote desktop session is being killed as >>>I exit the >>>TightVNC client which btw, is a Windows client. >>> >>> >>> >>>On windows this happens by default. I found the following on >>>the RealVNC >>>site: >>> >>>http://www.realvnc.com/products/free/4.1/x0.html >>> >>>but that is not quite what would be ideal. Again, I would >>>like to startup >>>a desktop session to which I can reconnect to later and find >>>everything >>>that had been spawned as I left it. Is there something easy >>>that I have >>>overlooked ? >>> >>>tia, >>> >>>-Charles >>> >>> >>> >>> >>> >>> >>> >>>-- >>>Charles A. Monteiro >>> >>> >>>------------------------------------------------------- >>>SF.Net email is Sponsored by the Better Software Conference & EXPO >>>September 19-22, 2005 * San Francisco, CA * Development >>>Lifecycle Practices >>>Agile & Plan-Driven Development * Managing Projects & Teams * >>>Testing & QA >>>Security * Process Improvement & Measurement * >>>http://www.sqe.com/bsce5sf >>>___________________________________________________________ >>>TightVNC mailing list, VNC...@li... >>>To change your subscription or to UNSUBSCRIBE, please visit >>>https://lists.sourceforge.net/lists/listinfo/vnc-tight-list >> >> >> >>------------------------------------------------------- >>SF.Net email is Sponsored by the Better Software Conference & EXPO >>September 19-22, 2005 * San Francisco, CA * Development Lifecycle >>Practices >>Agile & Plan-Driven Development * Managing Projects & Teams * Testing & >>QA >>Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf >>___________________________________________________________ >>TightVNC mailing list, VNC...@li... >>To change your subscription or to UNSUBSCRIBE, please visit >>https://lists.sourceforge.net/lists/listinfo/vnc-tight-list > > > >-- >Charles A. Monteiro > > >------------------------------------------------------- >SF.Net email is Sponsored by the Better Software Conference & EXPO >September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices >Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA >Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf >___________________________________________________________ >TightVNC mailing list, VNC...@li... >To change your subscription or to UNSUBSCRIBE, please visit >https://lists.sourceforge.net/lists/listinfo/vnc-tight-list |