Ubuntu
sysvinit package

sysvinit's ondemand and cpufrequtils init scripts conflict

Bug #833594 reported by pezcurrel on 2011-08-25

This bug report is a duplicate of: Bug #911206: /etc/init.d/ondemand unconditionally overrules /etc/init.d/cpufrequtils. Edit Remove

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	cpufrequtils (Ubuntu)	Confirmed	Undecided	Unassigned
	sysvinit (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

On ubuntu 10.04, /etc/init.d/ondemand script (from package initscripts) can conflict with /etc/init.d/cpufrequtils (package cpufrequtils)
By default, they both set ondemand governor for every cpu(core), using an internal variable.
If one changes this variable only in /etc/init.d/cpufrequtils to, say, "performance", at first the cpu governor will be set to performance, but then, after the "sleep 60" which is set in /etc/init.d/ondemand, /etc/init.d/ondemand will set it back to ondemand.
I think both scripts should instead read a global variable from a global config file (eg. /etc/default/cpufreq_governor).

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-05-11:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in sysvinit (Ubuntu):
status:	New → Confirmed

Shahar Or (mightyiam) on 2015-07-31

affects:	sysvinit (Ubuntu) → cpufrequtils (Ubuntu)
Changed in sysvinit (Ubuntu):
status:	New → Confirmed
summary:	- ondemand initscript conflicts with cpufrequtils initscript + sysvinit's ondemand and cpufrequtils init scripts conflict