Re: XForms: Forking a child (again)

Steve Lamont (spl@szechuan.ucsd.edu)
Tue, 2 Jun 98 17:10:09 PDT

# To subscribers of the xforms list from spl@szechuan.ucsd.edu (Steve Lamont) :

> Telling anything to X after the fork will cause problems, because
> at one point (after the fork) both processes will share the
> X connection file descriptor, which is VERY BAD.
> When you call fl_finish() in the child, that's what happens!

Again, you can close the connection in the child explicitly by getting
the connection number and issuing a close(). This will, of course,
terminate any interaction with the server. If you do a fork()
followed by an exec*() the connection will automatically be closed
since the X server connection is marked close on exec.

spl
_________________________________________________
To unsubscribe, send the message "unsubscribe" to
xforms-request@bob.usuf2.usuhs.mil or see
http://bob.usuf2.usuhs.mil/mailserv/xforms.html
XForms Home Page: http://bragg.phys.uwm.edu/xforms
List Archive: http://bob.usuf2.usuhs.mil/mailserv/list-archives/