FS#67709 - [cpupower] Add ConditionVirtualization=!container to the cpupower.service file
Attached to Project:
Community Packages
Opened by Jakub Klinkovský (lahwaacz) - Monday, 24 August 2020, 21:06 GMT
Last edited by Sébastien Luttringer (seblu) - Wednesday, 21 October 2020, 01:24 GMT
Opened by Jakub Klinkovský (lahwaacz) - Monday, 24 August 2020, 21:06 GMT
Last edited by Sébastien Luttringer (seblu) - Wednesday, 21 October 2020, 01:24 GMT
|
Details
Currently you need 2 different configurations if you manage
a system for bare-metal hardware and containers (e.g. for
testing). The problem is that if you attempt to start
cpupower.service inside a container, it will fail. For these
cases systemd offers the ConditionVirtualization option [1]
which can be set to !container to avoid starting the service
inside containers. I think this is a sensible default option
for the packaged service file.
[1] https://www.freedesktop.org/software/systemd/man/systemd.unit.html#ConditionVirtualization= |
This task depends upon
Closed by Sébastien Luttringer (seblu)
Wednesday, 21 October 2020, 01:24 GMT
Reason for closing: Implemented
Additional comments about closing: cpupower-5.9-1
Wednesday, 21 October 2020, 01:24 GMT
Reason for closing: Implemented
Additional comments about closing: cpupower-5.9-1