[systemd-devel] Starting units when a port is available for connections
Lennart Poettering
lennart at poettering.net
Thu Jun 18 11:20:35 PDT 2015
On Thu, 28.05.15 18:35, Adam Zegelin (adam at instaclustr.com) wrote:
>
> > On 27 May 2015, at 8:40 pm, Andrei Borzenkov <arvidjaar at gmail.com> wrote:
> >
> > Hmm ... this sounds suspiciously like what D-Bus does. Did you consider
> > using D-Bus in your application?
> >
> > But for now there is no way to express such dependency in systemd;
> > D-Bus being exception, you can make services dependent on D-Bus end
> > points.
>
> I’ve considered it now :) I communicate with systemd via D-Bus for
> starting & stopping services.
>
> How does one write a service unit that depends on a D-Bus endpoint?
> Is this supported by systemd, or is this an application level thing?
> I’m unable to find anything in the systemd docs about creating
> dependencies on D-Bus endpoints.
The general mode of operation with dbus is that you just talk to
services, and should they not be started yet then they will be and the
msg queued...
Lennart
--
Lennart Poettering, Red Hat
More information about the systemd-devel
mailing list