Red Hat Bugzilla – Bug 817025
numad: systemctl can't start/stop numad.service if executing numad command
Last modified: 2014-01-12 19:01:58 EST
Description of problem:
if you start numad through '# numad', then systemctl can't control the numad.service.
Version-Release number of selected component (if applicable):
numad version: 20120305b
Steps to Reproduce:
[root@ZhoupingLiu numad]# numad
[root@ZhoupingLiu numad]# systemctl start numad.service
[root@ZhoupingLiu numad]# systemctl status numad.service
numad.service - numad - The NUMA daemon that manages application locality.
Loaded: loaded (/usr/lib/systemd/system/numad.service; enabled)
Active: inactive (dead) since Thu, 26 Apr 2012 14:46:45 +0800; 9s ago
Process: 9881 ExecStart=/usr/bin/numad -i $INTERVAL (code=exited, status=0/SUCCESS)
and I'm sure numad.service is always running.
systemctl can't control numad.service.
systemctl can control numad.service
*** Bug 818460 has been marked as a duplicate of this bug. ***
I would blame systemd, as I can do the same with e.g. slapd (Openldap server that also provides a service file and can be run manually). I think that running a service manually and controlling it through systemctl just don't work together.
(In reply to comment #2)
> I think that running a service manually and controlling it through systemctl
> just don't work together.
Correct. When you run "numad" from your shell, you are not really running a "service" in systemd's view. You are merely running a process in your login session. Note that that process will inherit certain parts of your environment, and it will not be running in its own cgroup. Proper clean environment in which services are running is considered a feature of systemd.
So in general do not start daemons outside of systemd services.
Not a bug then.