Path: utzoo!utgpu!watserv1!watmath!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!apple!agate!shelby!unixhub!ditka!teda!mikel
From: mikel@teda.UUCP (Mikel Lechner)
Newsgroups: comp.windows.x
Subject: Re: Resources & Forking
Message-ID: <17491@teda.UUCP>
Date: 29 Nov 90 19:12:46 GMT
References: <1990Nov4.070135.11971@vicorp.com> <1990Nov28.191838.4990@arnor.uucp> <3673@exodus.Eng.Sun.COM>
Sender: news@ditka.chicago.COM
Lines: 24

argv@turnpike.Eng.Sun.COM (Dan Heller) writes:

>In article <1990Nov28.191838.4990@arnor.uucp> gah@ibm.com (Gary Hoffman) writes:

>> 2)  If I open a display, then fork I presume both processes are
>>     sharing a connection to the server.
>Nope.  Just the parent.  The child's connection *must* be closed.
>You can reopen a -new- connection to the server and rebuild widgets
>or do whatever you want.

Actually the child process could keep the connection, but in this case the
parent should close it's connection and obtain a new connection to the
X server.  Both cannot use the same connection.

Also, if the child keeps the connection it cannot "exec" a new program
and keep the connection, since this would almost certainly confuse the
client code in the new program.


-- 
Mikel Lechner			UUCP:  teda!mikel
Teradyne EDA, Inc.
5155 Old Ironsides Drive	| If you explain so clearly that nobody
Santa Clara, Ca 95054		| can misunderstand, somebody will.