retitle 433202 Please set default policy earlier than the various cpufreq deamons thanks
On Sun, Jul 15, 2007 at 02:58:33PM +0200, Cesare Leonardi wrote: > Mattia Dongili wrote: >>> Since cpufrequtils seems to be a subset of cpufreqd, and of each of them >>> main function's is to set the cpufreq governor that a cpu have to use >>> (and its options), shouldn't they conflict with each other? >> no, cpufreqd does it dynamically, cpufrequtils statically and also >> includes an utility to inspect the current state (cpufreq-info). > > Yes, i know, but it creates an init scripts that ovelaps with that of > cpufreqd. Maybe cpufrequtils should not create an initscript if cpufreqd is no, maybe cpufreqd should start after cpufrequtils. Or simply cpufrequtils start earlier to avoid also breaking other policy deamons. > installed. Or should be a mechanism to make cpufrequtils to do nothing on > startup (a variable on /etc/default/cpufrequtils?). there is already. >>> As now the package's description is not very clear on what the package do >> what's not clear about that? > > See #433203. ;-) the description you provide is wrong. But leave that to the other bug you submitted. ciao -- mattia :wq! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
