Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#89 closed enhancement (fixed)

xvnc status updates by watching server output (like nx does) — at Version 2

Reported by: Antoine Martin Owned by: Antoine Martin
Priority: major Milestone: 0.9.2
Component: Client Keywords:
Cc:

Description (last modified by Antoine Martin)

We should probably watch the output of the Xvnc process like we do for NX.
Looks like we can detect if the session is connected or not:
vncext: Listening for VNC connections on port 16064
Means no need to test using a wait_for_socket.
Connections: accepted: 127.0.0.1::51920
Means we can remove the need for the client to set the CONNECTED status.
Connections: closed: 127.0.0.1::51920 (Clean disconnection)
As above for AVAILABLE.


Log Xvnc output to file ~/.Xvnc/:DISPLAY.log

Note: the code has only been tested with tigervnc...

Change History (2)

comment:1 Changed 14 years ago by Antoine Martin

Resolution: fixed
Status: newclosed

done in r1920, added disconnection detection in r1925

Last edited 13 years ago by Antoine Martin (previous) (diff)

comment:2 Changed 14 years ago by Antoine Martin

Description: modified (diff)
Note: See TracTickets for help on using tickets.