|
KindleVNCviewer has a constantly reconnecting loop because of such issues. However the dropping of the SSH connection is a problem then. Unfortunately, I don't have neither a K3 nor a KDX for testing anymore. I remember that there was a network watching daemon on those devices that would drop long standing connections. This was not true for the SSH port, as far as I remember.
That said, and looking at the howto you mentioned, I see some things to try out. First, try switching from telnet to use SSH.
You might also want to try the kindlevncviewer call with ">/dev/null 2>&1 &" instead of just "&" at the end. This will redirect the output to the neverland, possibly avoiding problems when the telnet/SSH connection is dead and the kindlevncviewer is still running. At some point it will fill the output buffer and catch a signal it cannot handle.
I found it most stable, though, to tunnel the VNC connection through a SSH session. I'm pretty sure I talked about that at length in the kindlevncviewer thread (but some people have difficulties to grasp the concept of TCP connection tunnels via SSH, however, there are explanations on the web available and they are probably better than what I can deliver. They are not easy to grasp, so take your time).
|