** Package changed: sysvinit (Ubuntu) => cpufrequtils (Ubuntu)
** Also affects: sysvinit (Ubuntu)
Importance: Undecided
Status: New
** Changed in: sysvinit (Ubuntu)
Status: New => Confirmed
** Summary changed:
- ondemand initscript conflicts with cpufrequtils initscript
+ sysvinit's ondemand and cpufrequtils init scripts conflict
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/833594
Title:
sysvinit's ondemand and cpufrequtils init scripts conflict
Status in cpufrequtils package in Ubuntu:
Confirmed
Status in sysvinit package in Ubuntu:
Confirmed
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/cpufrequtils/+bug/833594/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
