On Tue, 23.08.11 08:14, Richard Shaw (hobbes1069@xxxxxxxxx) wrote: > > Lennart, > > Here's the response from upstream: > """ > On Mon, Aug 22, 2011 at 04:09:34PM -0500, Richard Shaw wrote: > > How exactly does spacenavd interface with applications? Is it some > > sort of socket? > > Spacenavd provides two interfaces to applications: > - The libspnav-only interface which doesn't require a running X server > uses a UNIX domain socket to communicate with applications. So the daemon listens on a local socket. That means it's quite important that systemd waits with starting the next service until your daemon finished starting up (and hence finished establishing the listening socket), so that the next service can rely that the listening socket is connectable. That means Type=forking is a working choice. In all cases using socket activation is preferable since it increases parallelization, robustness and simplicity, but this requires patching, as mentioned. Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
