Infinite Loop (RealVNC)

Seak, Teng-Fong tfseak "at"
Tue Mar 16 09:40:01 2004

> -----Message d'origine-----
> De : Wayne Ivory [mailto:waynei "at"]
> Envoyi : mardi 16 mars 2004 01:38
> @ : vnc-list "at"
> Objet : Infinite Loop (RealVNC)
> This is not really a question, just a "heads up" for interested parties.
> Not sure if it's been reported before.
> Yesterday one of my IT colleagues went to do some work on one of our
> production servers.  Whilst there he wanted to check something on his own PC
> and rather than walk back to the office he just VNC'd to his desktop.  But
> he forgot that earlier he had VNC'd from his desktop to the production
> server in question and left the session open.  What he experienced next was
> a cascading of windows that he could only stop by closing the WinVNC icon in
> the system tray.

	He could have solved the problem differently.  First, he could have just closed the viewer on the production server screen.  Then he could have closed connection instead of closing down VNC server.

> This behaviour is understandable I suppose but not really ideal.  I'm not
> even sure what would be a reasonable response to this situation

	The response is: Be smart, or drink a cup of coffee if he's not totally waken up :)

> - preventing
> the second connection seems a bit harsh; perhaps the first connection should
> get terminated??

	Given that both viewer and server are two separate programmes, I don't think they communicate in the way you think they are.  Sure, in programming, almost everything is possible.  It's just a matter of time and effort, but does it deserve this time and effort?