[systemd-devel] Repeated service stop/start accumulates process in status output

Andrey Borzenkov arvidjaar at gmail.com
Sun Jan 23 07:44:38 PST 2011


Somewhat unexpected; is it really intentional?

{pts/1}% systemctl status alsa.service
alsa.service - LSB: Launch alsa sound system
          Loaded: loaded (/etc/rc.d/init.d/alsa)
          Active: active (exited) since Sun, 23 Jan 2011 17:53:39
+0300; 47min ago
          CGroup: name=systemd:/system/alsa.service
{pts/1}% sudo /etc/init.d/alsa stop
Stopping alsa (via systemctl):                                  [   ОК  ]
{pts/1}% systemctl status alsa.service
alsa.service - LSB: Launch alsa sound system
          Loaded: loaded (/etc/rc.d/init.d/alsa)
          Active: inactive (dead) since Sun, 23 Jan 2011 18:41:52 +0300; 3s ago
         Process: 15384 (/etc/rc.d/init.d/alsa stop, code=exited,
status=0/SUCCESS)
          CGroup: name=systemd:/system/alsa.service
{pts/1}% sudo /etc/init.d/alsa start
Starting alsa (via systemctl):                                  [   ОК  ]
{pts/1}% systemctl status alsa.service
alsa.service - LSB: Launch alsa sound system
          Loaded: loaded (/etc/rc.d/init.d/alsa)
          Active: active (exited) since Sun, 23 Jan 2011 18:42:07 +0300; 2s ago
         Process: 15384 (/etc/rc.d/init.d/alsa stop, code=exited,
status=0/SUCCESS)
         Process: 15538 (/etc/rc.d/init.d/alsa start, code=exited,
status=0/SUCCESS)
          CGroup: name=systemd:/system/alsa.service


More information about the systemd-devel mailing list