Sorry to hear... If I may ask, is an OS upgrade possible? If not, depending on what you are needing and the version of VNC you are using, you could enable sharing of display :0 using the vnc.so library loaded via the XF86Config. What you get with the sharing of display :0 is effectively showing the physical console remotely via VNC and it doesn't go through inetd, but that version of RedHat+VNC may require the xf4vnc package (http://xf4vnc.sourceforge.net/) . I have not used that package directly. On the Linux distros where I have exported display :0, the proper package + libraries were already installed in my setup.
Regards. >>> On Mon, May 15, 2006 at 6:25 PM, in message <[EMAIL PROTECTED]>, "Bovy, Stephen J" <[EMAIL PROTECTED]> wrote: > Hi Jeff > > Well I think you are correct (: > > I did a search on redhat 6.2 and inetd and found several bug reprots > > unfortunately these are old outdated redhat bug reports and the ftp > links to the fix packages > no longer exist > > and I have not been able to find a redhat archival ftp mirror with the > old update repository (sigh) > > Now another slightly different question > > which vnc implementation is faster ?? I do not want to start any flame > wars (: > > > ----- Original Message----- > From: Jeff Vincent [mailto:[EMAIL PROTECTED] > Sent: Friday, May 12, 2006 3:47 PM > To: Bovy, Stephen J > Cc: vnc- [EMAIL PROTECTED] > Subject: RE: inetd and port 59(xx) gives me empty testpatterngreyscreen > ??? > > <Replying to all> ;- ) > > I don't recall right off what the "unix" means in the font path, but is > the URI format required to connect to a broadcasting font server. I'll > look for the info later. > > As far as /etc/services, I thought that /etc/services was mandatory for > using Xvnc in inetd mode because they work together. /etc/services > defines a service name and tells the inetd superserver which port to > listen on and which network protocols it uses. Then when a request > comes in that matches, inetd uses the info from /etc/inetd.conf to know > how to launch the process for that service. > > Theoretically, wait mode is for persistent sessions, but I've never used > it. I have always used nowait mode or configured the sharing of > display:0. > > As I type this, I am vaguely recalling an issue with inetd not working > correctly on a certain Linux distro...maybe this is that case...hmm. I > need to research that one. > >>>> On Fri, May 12, 2006 at 4:09 PM, in message > <[EMAIL PROTECTED]>, "Bovy, Stephen > J" > <[EMAIL PROTECTED]> wrote: >> Thanks Jeff, >> >> Yup, basically been there done almost all of that stuf >> >> I was running as root that did not help >> >> Yes I know XDMCP is working I connect in using several different x- > win >> managers such as cygwin x- win >> >> yes I have the font server up and running >> >> xdeep32 is another free x- win manager works great (: >> >> the only thing I have not tried yet is using etc/services... >> >> I was trying "nowait" to establish a persistent session >> >> "wait" works great as long as I use port ( 5900 ) >> >> hmm I guess I could try adding - fp unix/:7100 what does the unix/ > mean >> ??? >> >> Hey Jeff please try reply- all so that you include the mail- list in > our >> thread discussion >> >> this mail list is kind- of weird most mail lists do not include the >> subscribers email it is kind of confusing >> >> >> >> >> Stephen Bovy >> Computer Associates >> 6100 Center Drive >> Suite 700 >> Los Angeles, CA 90045 >> Tel: (310) 957- 3930 >> Fax: (310) 957- 3917 >> Mobile: (818) 352- 9917 >> e- mail: [EMAIL PROTECTED] >> ----- Original Message----- >> From: Jeff Vincent [mailto:[EMAIL PROTECTED] >> Sent: Friday, May 12, 2006 2:40 PM >> To: Bovy, Stephen J >> Subject: RE: inetd and port 59(xx) gives me empty test > patterngreyscreen >> ??? >> >> Boy, it's been a while for me for those older versions. Here is a > brain >> dump...it may not all apply to RH 6.2 or your situation, but > something >> may help (shotgun approach ;- ). This is all based on past usage of > VNC >> 3.2.x versions. >> >> Here is a couple of lines from the /etc/services and /etc/inetd.conf >> files I normally include when I do similar things. >> >> #/etc/services >> vnc- 1280x1024x24 5973/tcp >> >> #/etc/inetd.conf >> vnc- 1024x768x24 stream tcp nowait root /usr/local/bin/Xvnc Xvnc - > inetd >> - query localhost - once - geometry 1024x768 - depth 24 >> >> In this configuration, connect using the VNC service 192.168.0.22:73 >> (substitute your IP). >> >> I wasn't worried about security in our labs where I use this a lot so > I >> use "root" as the user to run the Xvnc binary. There can be rights >> issues for Xvnc and the 'nobody' or 'james' users. Some operating >> systems don't allow users with a UID > 1024 to access/run certain >> things. You might try adding root just to eliminate that issue >> >> Also, I have known issues when the X Font server wasn't running > (xfs), >> but don't recall if that is an issue on RH 6.2. Once you get xvf to >> start when booted, then you can add: - fp unix/:7100 (or whatever > port >> yours is using). >> >> If you are running in inetd mode, you shouldn't need to require the >> '- passwordfile' option as the inetd method gives you at a new > session >> with a GUI login prompt. There may be reasons to require a password > to >> even attach via VNC, I just haven't seen it done. >> >> As far as XDMCP being enabled...I've never used xdeep32 so I don't > know >> how it works. But as a sanity check, I'd still verify the display >> manager settings. In that version of RH, if it is running gdm I > think >> it uses the xdm configuration files in /etc/X11/xdm. If there is a > file >> called xdm- config, comment out the last line >> >> ! DisplayManager.requestPort: 0 >> >> and then in Xaccess, uncomment the line: >> >> * #any host can get a login window >> >> Newer versions of gdm use a gdm.conf file. If you are using kdm, > there >> might be a file called kdmrc that you can look at. I check the > display >> manager I am running by doing 'ps - ef | grep dm' and see what it > finds. >> >> Let us know how it goes. >> >> - Jeff >> >>>>> On Fri, May 12, 2006 at 2:22 PM, in message >> <[EMAIL PROTECTED]>, "Bovy, > Stephen >> J" >> <[EMAIL PROTECTED]> wrote: >>> Thanks for responding >>> >>> I am using redhat 6.2 (yes I know it is old) (: >>> >>> IN this case I think the default is gdm >>> >>> But XDMCP is enabled and working >>> >>> I am using win32 xdeep32.exe x- win manager to connect to xdmcp >> desk >>> top no problem >>> >>> And if you re- read my email >>> >>> inetd with port (5900) works perfectly with - query xxx - once >>> >>> the only time things get "buggy" is when I try to use { 59(xx) } > as >> a >>> port address (: >>> >>> >>> >>> Stephen Bovy >>> Computer Associates >>> 6100 Center Drive >>> Suite 700 >>> Los Angeles, CA 90045 >>> Tel: (310) 957- 3930 >>> Fax: (310) 957- 3917 >>> Mobile: (818) 352- 9917 >>> e- mail: [EMAIL PROTECTED] >>> ----- Original Message----- >>> From: Jeff Vincent [mailto:[EMAIL PROTECTED] >>> Sent: Friday, May 12, 2006 1:04 PM >>> To: Bovy, Stephen J >>> Subject: Re: inetd and port 59(xx) gives me empty test pattern >>> greyscreen ??? >>> >>> Usually means XDMCP is not enabled. What Linux distro you running >> and >>> which display manager (gdm, kdm, etc.) ? >>> >>>>>> On Fri, May 12, 2006 at 1:28 PM, in message >>> <[EMAIL PROTECTED]>, "Bovy, >> Stephen >>> J" >>> <[EMAIL PROTECTED]> wrote: >>>> 5950 stream tcp nowait nobody /usr/local/bin/Xvnc Xvnc - inetd - >>> query >>>> localhost - once securitytypes=none >>>> >>>> Gray Screen on first connection, xdm on subsequent connections >>>> >>>> 5951 stream tcp wait james /usr/local/bin/Xvnc Xvnc - inetd - >> query >>>> localhost - once passwordFile=/home/james/.vnc/passwd >>>> >>>> Gray screen all the time >>>> >>>> The only thing that works consistenly is: >>>> >>>> 5900 stream tcp nowait nobody /usr/local/bin/Xvnc Xvnc - inetd - >>> query >>>> localhost - once securitytypes=none >>>> _______________________________________________ >>>> VNC- List mailing list >>>> VNC- [EMAIL PROTECTED] >>>> To remove yourself from the list visit: >>>> http://www.realvnc.com/mailman/listinfo/vnc- list >> _______________________________________________ >> VNC- List mailing list >> VNC- [EMAIL PROTECTED] >> To remove yourself from the list visit: >> http://www.realvnc.com/mailman/listinfo/vnc- list > _______________________________________________ > VNC- List mailing list > VNC- [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
