Correct way to handle fork/exec errors with DBusServer

Havoc Pennington havoc.pennington at gmail.com
Thu Jan 8 08:55:01 PST 2009


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


More information about the dbus mailing list