Mattia Dongili wrote:
no, maybe cpufreqd should start after cpufrequtils. Or simply
cpufrequtils start earlier to avoid also breaking other policy deamons.
Seems a sensible solution.
installed. Or should be a mechanism to make cpufrequtils to do nothing on
startup (a variable on /etc/default/cpufrequtils?).
there is already.
Yes, you are right, sorry.
See #433203. ;-)
the description you provide is wrong. But leave that to the other bug
you submitted.
Ok, i'll wait for your comment on that bug report.
Many thanks for your good work.
Ciao.
Cesare.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
