[systemd-devel] socket / service dependency

Lennart Poettering lennart at poettering.net
Thu Mar 30 14:09:17 UTC 2017

On Mon, 20.03.17 12:38, Ken Bass (kbass at kenbass.com) wrote:

> I thought I followed the instructions (using Centos 7 - I believe
> systemd219) ... I am running a local news server (innd.service).
> I needed to add an additional inetd style daemon for nnrpd to support SSL.
> See files below. Using the BindTo and After seems proper since I never want
> nnrpd running unless innd is already started/running. If innd is stopped, i
> want to be sure nnrpd is stopped. Initially this worked fine. But if I stop
> the innd service, and then start it again, the nnrpd.socket is not started.
> How do I handle this?
> I created a drop in file for innd with a Before/Wants of nnrpd. This
> sometimes works, but normally I get 'Job innd.service/start deleted to break
> ordering cycle starting with nnrpd.socket/start'. What is the proper way to
> do this.

Please provide the full log excerpt around this message, it shows you
exactly what the ordering dep cycle is.

> /etc/systemd/system/innd.d/innd.conf

This path doesn't look right?

> /etc/systemd/system/nnrpd at service

Neither does this one.


Lennart Poettering, Red Hat

More information about the systemd-devel mailing list