Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!sdd.hp.com!hplabs!hpfcso!hpfcmgw!chan
From: chan@hpfcmgw.HP.COM (Chan Benson)
Newsgroups: comp.windows.x.motif
Subject: Re: killing a "dead" window in mwm
Message-ID: <13680001@hpfcmgw.HP.COM>
Date: 12 Jul 90 16:37:28 GMT
References: <5927@aplcen.apl.jhu.edu>
Organization: HP Fort Collins, CO
Lines: 13

> I recently posted an article about killing a dead window. What I 
> meant was if you start up a Motif application and fork and exec
> a program and try to kill the motif application while the child
> process is still running, the motif window will still be there
> even if the child finishes. Try it and see. Other than making sure
> the child is finished (obvoiusly), is there a way to get rid of
> the window.

You need to set the close-on-exec flag on the file descriptor associated
with your connection to the server (ConnectionNumber(dpy)). Alternatively
you could manually close it after you fork.

			-- Chan