mirror of
https://github.com/systemd/systemd.git
synced 2024-11-14 15:21:37 +03:00
bb11271068
A service that only sets the scheduling policy to round-robin fails to be started. This is because the cpu_sched_priority is initialized to 0 and is not adjusted when the policy is changed. Clamp the cpu_sched_priority when the scheduler policy is set. Use the current policy to validate the new priority. Change the manual page to state that the given range only applies to the real-time scheduling policies. Add a testcase that verifies this change: $ make test-sched-prio; ./test-sched-prio [test/sched_idle_bad.service:6] CPU scheduling priority is out of range, ignoring: 1 [test/sched_rr_bad.service:7] CPU scheduling priority is out of range, ignoring: 0 [test/sched_rr_bad.service:8] CPU scheduling priority is out of range, ignoring: 100
9 lines
149 B
Desktop File
9 lines
149 B
Desktop File
[Unit]
|
|
Description=Bad sched priority for RR
|
|
|
|
[Service]
|
|
ExecStart=/bin/true
|
|
CPUSchedulingPolicy=rr
|
|
CPUSchedulingPriority=0
|
|
CPUSchedulingPriority=100
|