No, this is what you would do in C for any X related program that forks.
As you may know, X programs talk to the X server through a network socket
connection. This is represented as a file descriptor for the process.
When you fork the process, both processes have file descriptors for this
one network connection.
When one process exits with the exit() call, it will attempt to clean up
this file descriptor and shut down the network connection. Since this is
not what we want for the child process, we call _exit() instead. Its not
a bug, it's a feature :) (Anyway, it can't be fixed in GTK).
James Henstridge.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
On 23 Feb 1999, Hrvoje Niksic wrote:
> James Henstridge <[EMAIL PROTECTED]> writes:
>
> > You would get the same problem if you wrote a C GTK+ program that
> > forked and you called exit(). In this case, you would call _exit()
> > which bypasses all atexit handlers.
>
> Should I raise this question on the Gtk+ list?
> To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
>
To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
