Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!ucbvax!bloom-beacon!dont-send-mail-to-path-lines
From: gildea@expo.lcs.mit.EDU (Stephen Gildea)
Newsgroups: comp.windows.x
Subject: Re: Allocating Colors in a forked process
Message-ID: <9101071511.AA26748@excalibur.lcs.mit.edu>
Date: 7 Jan 91 15:11:00 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 17


    Date: 3 Jan 91 16:35:42 GMT
    From: etaylor@wilkins.iaims.bcm.tmc.edu (Eric Taylor)

    When you fork, you must close the connection
    to X in your child process, then reopen it.  Then, to the
    X server, you are two completely different clients free to
    do whatever you desire.

    I am not sure of the supposed behavior of a connection
    after a process forks, but I assume it is undefined because
    of different implementations (i.e. VAX)

The R4 implementation of Xlib sets the close-on-fork bit for the
connection, so this problem never comes up.

 < Stephen