kernel-5.10/cpupower.path

[Unit]
Description=cpupower - wait for the list of frequency governors
After=syslog.target

[Path]
PathExists=/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors

[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			`[Unit]`
			`Description=cpupower - wait for the list of frequency governors`
			`After=syslog.target`

			`[Path]`
			`PathExists=/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors`

			`[Install]`
			`WantedBy=multi-user.target`