Alan, You don't want to start vncconfig when a viewer connects, but when the desktop is started, and then just leave it running. You can do this my adding the following line to your xstartup script:
vncconfig -nowin & Which will run vncconfig invisibly and in the background, within the Xvnc desktop. Regards, Wez @ RealVNC Ltd. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Alan A. Dunwell > Sent: 05 July 2005 21:26 > To: [email protected] > Subject: Xvnc via xinetd and vncconfig > > Howdy VNC gang, > > I understand that in order to get VNC 4.1.1 to allow > clipboard xfer one > needs to have vncconfig running. I know that I can just start > vncconfig > after login in, but this uses up a term window and of course > the users > will forget till it is needed. > > I am running Xvnc via xinetd.d on RHEL3.x and would like to > auto-start > vncconfig when any vncviewer connects to the port. I have looked > through the FAQ, back-issues/archives of the list, the man pages on > vncconfig and Xvnc, and the Xvnc -help but did not see any > options that > might be included in the parameter line. I'm probably just missing > something here but is this possible? > > Thanks, > Alan D. > _______________________________________________ > VNC-List mailing list > [email protected] > To remove yourself from the list visit: > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
