Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determine failed network connection and kick clients #216

Open
moebassist opened this issue Jan 9, 2023 · 0 comments
Open

Determine failed network connection and kick clients #216

moebassist opened this issue Jan 9, 2023 · 0 comments

Comments

@moebassist
Copy link

I Start a VNC server with the following:

x11vnc -display :0 -ping 30 -auth /root/.Xauthority -forever -loop -noxdamage -repeat -rfbauth /root/.vnc/passwd -rfbport 5900 -shared

When remote viewing via client, if I physically disconnect the client the server still thinks I have a client connected - presumably because the TCP connection is just sitting idle and no data is being requested - which is valid.

How can I force the VNC server to close the client when it's been idle for a time period? I attempted to use '-ping 30' to force a 1x1 update every 30 seconds, in the hope that the server would force a close upon failure, but this doesn't work. When I x11vnc -query ping the answer comes back as 0 (disabled).

TigerVNC has 'Idletimeout'....does x11vnc have anything similar?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant