Xvnc -inetd

Gary Stainburn gary.stainburn "at" ringways.co.uk
Tue, 28 Aug 2001 09:36:23 +0000

Hi Evan,

The problem shutting down and the respawning problem after rebooting were 
caused by the KDE upgrade screwing my system. That is why I had to re-install 
from scratch, thus losing my then working xinetd VNC setup.

I now have a 'clean slate' setup from the installation CD's with the errata 
updates installed, but the xinetd VNC still isn't working.


On Sunday 26 August 2001  8:03 pm, you wrote:
> Looks like you may need to back up the error chain a little. Did you
> find out what caused the too rapid respawn? A reboot should not have
> that happen as it start from a clean slate.
> evan
> Gary Stainburn wrote:
> > On the KDE front, I downloaded the RH71 KDE and non-kde rpms from the KDE
> > site, then ran rpm -Uvh --nodeps *.  Once it finished, I couldn't do
> > anything, so I thought I'd reboot.  'shutdown -r now' segfaulted.
> > Smacking reset rebooted the box, then *everything* in my inittab failed
> > for respawning too fast.
> >
> > I think xinetd is doing something, because if I remove the services, I
> > get connection refused.
> >
> > I'm trying to connecting from linux with 'vncviewer gary:53' and from a
> > windows box with a link to 'vncviewer.exe /fullscreen /emulate3 gary:52'
> >
> > The linux box I  was trying to connect from was 'gary' so I assume it was
> > using the lo interface.  I've got no ipchains/iptables rules on.
> >
> > As far as I can see, I've got it exactly as I had it before, what I've
> > missed I can't guess.
> >
> > Gary

Gary Stainburn
This email does not contain private or confidential material as it
may be snooped on by interested government parties for unknown
and undisclosed purposes - Regulation of Investigatory Powers Act, 2000     
To unsubscribe, send a message with the line: unsubscribe vnc-list
to majordomo "at" uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html