[Bug 1564496] Comment bridged from LTC Bugzilla

[bugproxy]

------- Comment From brueckner at de.ibm.com 2016-04-04 08:33 EDT-------
(In reply to comment #12)
> Why a sub-package? Would it be acceptable to ship this in s390-tools, but
> with systemd unit disabled? That way if people want to use cpuplugd they
> would modify the config as suitable, and enable it with `systemctl enable
> cpuplugd`.

It is also fine to ship it with s390-tools.  The systemd unit might be
disabled.  I will take care to add the systemd unit in the upstream
s390-tools. Regarding the enablement of systemd units, can this be done
on a per unit base?  I mean, if you we add more and more systemd units
in future, how to control enablement of particular systemd units only.
(This is more a generic questions rather something on this BZ).

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to s390-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1564496

Title:
  s390: missing cpuplugd

Status in s390-tools package in Ubuntu:
  Triaged

Bug description:
  Requirement for : cpuplugd

  This also includes a configuration file, man-page, and init script.
  The suggested package concept is a subpackage of the s390-tools.

  This is a command and a set of rules in a configuration file to dynamically
  enable or disable CPUs. For Linux on z/VM, you can also dynamically add or
  remove memory.

  Sample debdiff to integrate the cpuplugd daemon as subpackage of the
  s390-tools

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1564496/+subscriptions