Hi, > How is it, that a factory which is not the original server of the > socket can be responsible for holding a socket open after the parent > has been killed? Are you leaking the fd to the child process when you fork?
look in /proc/PID-OF-CHILD/fd and see if you have an open reference to the socket there. If so, you might need to close the fd in the child after you fork, or set the close-on-exec bit using fcntl if the child eventually calls exec. _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list