Celebrating the 22th anniversary of the UltraVNC: https://forum.uvnc.com/viewtopic.php?t=38031
Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864

Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

server notification of viewer disconnect

Post Reply
coolbreeze22
Posts: 5
Joined: 2004-12-07 21:16

server notification of viewer disconnect

Post by coolbreeze22 »

Is there current functionality for notifying the server when a viewer has disconnected from it. Like a pop up window that says "[Viewer 1] has disconnected".

I'm using UltraVNC in a real time response kind of way, and it necessitates that if a client (server) is disconnected from the command center (viewer) then the client needs to stop what thier doing until the connection is reinstated.

Thanks,

PS: what could I do, or where could I look to find this answer for regular VNC as well?
coolbreeze22
Posts: 5
Joined: 2004-12-07 21:16

So this is what I did

Post by coolbreeze22 »

The vnc server uses more memory when it is connected then when it is sitting waiting for a connection. So, I wrote a repeating program that is launched when the connection is made. the program keeping checking the memory usage of the server process and pinging the viewer for connection. I display a message when the memory usage substantially drops, or the ping is disconnected for many seconds. Not elegant but it works
User avatar
Rudi De Vos
Admin & Developer
Admin & Developer
Posts: 6883
Joined: 2004-04-23 10:21
Contact:

Post by Rudi De Vos »

A possible other solution is to use a log checker....

If the log is active, you get the message, "disconnected"
in the server log.

On unix you can monitor a running log, so there should exist some equivalent on windows.


Monitor log
do "action" when "string happen"
This solution could also be used to monitor custom stuff...

If this should work, we could cleanup the debug logging and keep some essential messages in it.
Post Reply