The attached patch fixes P2 bugster CR #6871744. Currently GDM 2.20.10 sends SIGTERM to the Xserver when it exits. If the GDM daemon receives another signal telling it to stop, then it will try harder to kill the Xserver by sending it a SIGKILL.
This behavior causes problems on Solaris. Killing the Xserver with SIGKILL causes the console display to get messed up, and you can refer to CR #6871744 for more details. There really is no need to ever kill the Xserver with SIGKILL. In fact, the new GDM 2.21.x (and later) code never does this. This patch fixes the code so it just sends another SIGTERM signal. I have tested this code and it works as expected. I have also shared packages built with this patch with Sherry Moore, who reported the problem. She verifies that this fix resolves the problem, and GDM exits nicely once this patch is integrated. I would like to propose this fix goes into the 2.26 stable branch. Brian -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: gdm-13-no-sigkill.diff URL: <http://mail.opensolaris.org/pipermail/jds-review/attachments/20090923/90a04e6f/attachment.ksh> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: gdm.diff URL: <http://mail.opensolaris.org/pipermail/jds-review/attachments/20090923/90a04e6f/attachment-0001.ksh>
