I'm not an expert of this but since Debian Jessie daemons are managed by systemd
, I'd recommend you to use sytemd
instead of init.d
, and then use
systemctl
to keep an eye over your daemons. I find that systemctl
is great for monitoring, and probably there are even more tools on systemd
for doing this.
To finish responding your question, by using systemctl status <daemon>
you can know the status of a daemon, and I think that it also works for init.d
scripts.
rsm@matrice:~$ systemctl status alienware-kbl
● alienware-kbl.service - alienware-kbl daemon
Loaded: loaded (/usr/lib/systemd/system/alienware-kbl.service; enabled)
Active: active (running) since Sat 2015-07-04 10:30:17 CEST; 3h 7min ago
Main PID: 1024 (alienware-kbl)
CGroup: /system.slice/alienware-kbl.service
├─1024 /bin/bash /usr/bin/alienware-kbl --start-daemon
└─1029 /usr/bin/python2.7 /usr/share/alienware-kbl/Daemon.py --start-daemon
As a new/newbie programmer I find that making daemons over systemd
is much easier than over init.d