Correct way to handle fork/exec errors with DBusServer

[John Palmieri]

----- "Havoc Pennington" <havoc.pennington at gmail.com> wrote:

> Hi,
> 
> On Thu, Jan 8, 2009 at 11:44 AM, John Palmieri <johnp at redhat.com>
> wrote:
> > An issue with fork that we run into is that if you exit your child
> before exec'ing the DBusServer socket is cleaned up and the socket
> file is unlinked on the disk (assuming you are not using abstract
> sockets).
> 
> How does DBusServer unlink code ever run? We don't afaik install an
> atexit handler.
> 
> Havoc

On further investigation it looks like it might be the memory manager they are using which does some automagic reffing and unreffing.  I'm happy as long as it isn't in D-Bus.
 
--
John (J5) Palmieri
Software Engineer
Red Hat, Inc.