Public bug reported:

The PCP 4.0.0 packages for bionic do not automatically start PCP daemon

>From my research so far, I believe the reason for this is that PCP 4.0.0
ships both sysvinit scripts and systemd unit files (which simply call
the sysvinit scripts). The services are enabled in the postinstall via
"update-rc.d <daemon> defaults". It appears that the behavior for
"update-rc.d ... defaults" is different for generated units (sysvinit
only, where they do get enabled), versus when systemd units are
available (where they are not enabled and not generated).

After installing PCP packages, the systemd units have status (using
pmcd.service for this example, but it applies to app PCP daemons):

Loaded: loaded (/lib/systemd/system/pmcd.service; disabled; vendor
preset: enabled)

Running "update-rc.d pmcd defaults" results in no change to the status
(confirming that "defaults" does not enable the service):

Loaded: loaded (/lib/systemd/system/pmcd.service; disabled; vendor
preset: enabled)

After running "update-rc.d pmcd enabled", the service is correctly

Loaded: loaded (/lib/systemd/system/pmcd.service; enabled; vendor
preset: enabled)

The best answer is probably to use deb-systemd-helper, or other
appropriate systemd commands in the postinst when installing on a system
with systemd, instead of using the old update-rc.d commands which appear
to behave differently and in violation of the Debian policy manual,
which states: "The default behaviour is to enable autostarting your
package’s daemon."[1]


** Affects: pcp
     Importance: Unknown
         Status: Unknown

** Affects: pcp (Ubuntu)
     Importance: Undecided
         Status: New

** Tags: bionic

** Bug watch added: #454

** Also affects: pcp via
   Importance: Unknown
       Status: Unknown

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  PCP daemons do not start automatically for bionic

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to