On Wed, Jun 25, 2014, at 11:17 AM, David Shea wrote:
David Shea (2):
Remove surprises from X startup.
As soon as anything else in the process creates a GLib child watch, this
SIGCHLD handler is going to be overwritten. That may not matter here
since all we're trying to do is detect failure on startup, before we
start GTK+, but I think it'd be cleaner to use the GLib facilities from
the start.
Having it be exclusive sucks of course, but that's just Unix. See also
http://www.macieira.org/blog/2012/07/forkfd-part-4-proposed-solutions/