It is possible to configure a display manger to launch Xvnc instead the regular
Xserver. This works with xdm for example, but not with gdm.
Looking into it I found an old hack that was applied to Xvnc to work around a
LinuxThreads bug that is no longer needed. Removing this hack makes Xvnc and gdm
work together.
diff -ur vnc_unixsrc/Xvnc/programs/Xserver/os/connection.c
vnc_unixsrc-gurulabs/Xvnc/programs/Xserver/os/connection.c
--- vnc_unixsrc/Xvnc/programs/Xserver/os/connection.c Mon May 11 11:02:17 1998
+++ vnc_unixsrc-gurulabs/Xvnc/programs/Xserver/os/connection.c Tue Oct 15 16:22:27
+2002
@@ -379,7 +379,7 @@
BEGIN ORL VNC modification
Don't use SIGUSR1 - linuxthread uses this internally */
-/* REMOVE
+/* no longer true 10/15/02 */
if (OsSignal (SIGUSR1, SIG_IGN) == SIG_IGN)
RunFromSmartParent = TRUE;
ParentProcess = getppid ();
@@ -388,7 +388,6 @@
kill (ParentProcess, SIGUSR1);
}
}
-*/
/* END ORL VNC modification
================================================================*/
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
