kernel-6.1/cpupower.service

[Unit]
Description=Configure CPU frequency settings
After=syslog.target
ConditionPathExists=/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors

[Service]
Type=oneshot
RemainAfterExit=yes
EnvironmentFile=/etc/sysconfig/cpupower
ExecStart=/usr/bin/cpupower-start.sh

[Install]
WantedBy=multi-user.target
Also=cpupower.path
Automatic import for version 3.10.19-1 2013-11-16 00:27:01 +04:00			`[Unit]`
cpupower: Select the governor at start time rather than during install Should fix bug #4810. cpupower will now select the governor automatically during the start of the service, based on what is available. This can be overridden with the variables in /etc/sysconfig/cpupower (see the comments there). 2015-03-13 17:29:40 +03:00			`Description=Configure CPU frequency settings`
Automatic import for version 3.10.19-1 2013-11-16 00:27:01 +04:00			`After=syslog.target`
Make sure cpupower starts after the list of governors is available On EeePC 1015 PED (in Live mode), cpupower.service seemed to start too early, before /sys/devices/.../scaling_available_governors was there, and failed as a result. There were no such problems on faster machines, but still. Now cpupower.service will start only when 'scaling_available_governors' file is available. cpupower.path unit handles this. If CPU frequency scaling is not supported the file will never appear and cpupower.service will not start at all, which is natural. 2015-03-17 20:53:12 +03:00			`ConditionPathExists=/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors`
Automatic import for version 3.10.19-1 2013-11-16 00:27:01 +04:00
			`[Service]`
			`Type=oneshot`
			`RemainAfterExit=yes`
			`EnvironmentFile=/etc/sysconfig/cpupower`
cpupower: Select the governor at start time rather than during install Should fix bug #4810. cpupower will now select the governor automatically during the start of the service, based on what is available. This can be overridden with the variables in /etc/sysconfig/cpupower (see the comments there). 2015-03-13 17:29:40 +03:00			`ExecStart=/usr/bin/cpupower-start.sh`
Automatic import for version 3.10.19-1 2013-11-16 00:27:01 +04:00
			`[Install]`
			`WantedBy=multi-user.target`
Make sure cpupower starts after the list of governors is available On EeePC 1015 PED (in Live mode), cpupower.service seemed to start too early, before /sys/devices/.../scaling_available_governors was there, and failed as a result. There were no such problems on faster machines, but still. Now cpupower.service will start only when 'scaling_available_governors' file is available. cpupower.path unit handles this. If CPU frequency scaling is not supported the file will never appear and cpupower.service will not start at all, which is natural. 2015-03-17 20:53:12 +03:00			`Also=cpupower.path`