Xvnc does not react properly to SIGHUP when viewer is connected (bug?).

[Michel Van den Bergh]

This is another followup on my previous message on combining kdm (or
xdm) 
with Xvnc.

In my previous message I indicated that I had problems with with
relogins when adding

:2 local /usr/local/bin/Xvnc -depth 15 -geometry 800x600 :2

to my /etc/X11/xdm/Xservers file.

I think the problem is that at the end of a session xdm performs
a server reset and Xvnc (v3.3.3r1) does not react properly to that.

To see this perform the following experiment:

Xvnc :1 &
vncviewer :1 &
xterm -display :1 &

-Type in xterm window in viewer. Everything is fine.

-Find PID of Xvnc (with "ps aux |grep Xvnc"). Assume it is 1000

kill -s SIGHUP 1000

-xterm dies, as it should!

xterm -display :1 &

-Type in xterm windows in viewer. Surprise! The window only updates
if the mouse moves.

-Quit viewer. Oops Xvnc seems to have died.

=============

If we perform the same experiment without connecting the viewer then 
everything works as it should!

Best regards,
Michel

PS. As a workaround I solved my problem by not changing the Xserver file
but instead
starting Xvnc in inittab (as a respawning
process) with the options "-query localhost -once". This will query a
running
xdm or kdm process for an XDCMP session. However this means that if you
log
out, the viewer will quit (which might actually be good).


Perhaps a similar effect can be obtained by adding 

:2 local /usr/local/bin/Xvnc -once   :2

to the /etc/X11/xdm/Xservers file. I haven't tested this since I wasted
too much time on this already.
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to majordomo "at" uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------