#89 closed enhancement (fixed)
xvnc status updates by watching server output (like nx does)
Reported by: | Antoine Martin | Owned by: | Antoine Martin |
---|---|---|---|
Priority: | major | Milestone: | 0.9.2 |
Component: | Client | Keywords: | |
Cc: |
Description (last modified by )
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 15 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 Changed 15 years ago by
Description: | modified (diff) |
---|
Note: See
TracTickets for help on using
tickets.
done in r1920, added disconnection detection in r1925