> Have you checked the inetd log? Might need to turn it on or such.

Yes.  When I run inetd in debug mode, a good connect & disconnect looks
like this:

Sep  9 15:18:25 netfinity inetd: launching: 5900
Sep  9 15:18:25 netfinity inetd: accept: new socket 3
Sep  9 15:18:25 netfinity inetd: pid 24605: exec /usr/local/bin/Xvnc 
Sep  9 15:18:25 netfinity inetd: uid: 507  gid: 103 
Sep  9 15:18:25 netfinity inetd: groups: 103 100 102 
Sep  9 15:18:37 netfinity inetd: pid 24605, exit status 0

A problem looks like this:

Sep  9 15:18:41 netfinity inetd: launching: 5900
Sep  9 15:18:41 netfinity inetd: accept: new socket 3
Sep  9 15:18:41 netfinity inetd: pid 24626: exec /usr/local/bin/Xvnc 
Sep  9 15:18:41 netfinity inetd: uid: 507  gid: 103 
Sep  9 15:18:41 netfinity inetd: groups: 103 100 102 
Sep  9 15:18:41 netfinity inetd[24430]: pid 24626: exit status 1 
Sep  9 15:18:41 netfinity inetd: pid 24626, exit status 100

> > I prefer to use 5900.  There is no 'plain vncserver' to 
> conflict with, 
> > and by using 5900, the viewer does not have to specify the 
> > port/session number.  Ie, I can use "hostname" instead of 
> > "hostname:50".
> 
> Nice idea.
> What $DISPLAY value do you get? (just a qurious question ;-)

The first session is :2, the second simultaneous connection is :3, and
so on.  If :2 disconnects, the next connection is :2 again.

> You started (if I remember well) with a problem that only 
> happens when using the AT&T vncviewer. I know that has less 
> compression methods for rfb communication. Is it possible 
> that the handshake between server and viewer just takes a 
> (little/lot) longer? Try specifying the compression protocol 
> at both ends.

No, that's not it.  The problem is present with both AT&T and TightVNC
(at both ends).  After one of these failed connections, there is no Xvnc
program running on the server.  

I should point out that I have patched Xvnc to automatically start an
application, to avoid using xdm.  

Keep thinking!  Please.

-Lee Allen
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to