[Bug 833594] [NEW] ondemand initscript conflicts with cpufrequtils initscript

[dentament]

Public bug reported:

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).

** Affects: sysvinit (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/833594

Title:
  ondemand initscript conflicts with cpufrequtils initscript

Status in “sysvinit” package in Ubuntu:
  New

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).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/833594/+subscriptions