3 edited title
| link

systemctl fails to accurately report status of daemons if they were started via mechanism other than systemctl

2 edited tags
| link
1
source | link

systemctl fails accurately report status of daemons if they were started via mechanism other than systemctl

There are two mechanisms to start/stop my program "abc"

  1. systemctl service file inside /usr/lib/systemd/system/abc.service
  2. /etc/abc init script abc script will invoke all the daemons. But systemctl status is not accurate when I start/stop daemons using /etc/abc

To fix this, I've added Type=forking and added PIDFile directive. It solves the issue of the stop. systemctl status will show inactive when I stop the daemons using the abc init script. So the issue got fixed partially. But it will still be inactive when I start the daemons using abc init script.

How can I solve this issue? I tried to introduce an abc.path file which checks for the existence of a file and then notifies the service. But it isn't helping.

Using systemd 219.