cpufreqd 2.0.0-pre1 review
Downloadcpufreqd is meant to be a replacement of the speedstep applet you can find on some other OS, it monitors battery level, AC state and
|
|
cpufreqd is meant to be a replacement of the speedstep applet you can find on some other OS, it monitors battery level, AC state and running programs and adjusts the frequency of the processor according to a set of rules specified in the config file (see cpufreqd.conf (5)).
Installation:
1. `cd' to the directory containing the package's source code and type `./configure' to configure the package for your system. If you're using `csh' on an old version of System V, you might need to type `sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
Running `configure' takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with the package.
4. Type `make install' to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean'. To also remove the files that `configure' created (so you can compile the package for a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly for the package's developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
What's New in This Release:
implemented backward compatibility for the configuration file format (great!!)
automatically load plugins (if not configured) and rely on plugins initialization to probe the necessary stuff
the configure script now accepts --enable/disable options for plugns that need some sort of special support
ported the PMU plugin
added sensors plugin (you'll need userspace libs from lm-sensors)
fixed socket creation permissions
added the ability to allow a certain group to read/write to the socket
fixed looots of bugs
beautified logs
the "cpu" directive was wrong, now named "cpu_interval" run 'sed -i -e 's/^cpu=/cpu_interval=/' /etc/cpufreqd.conf' to fix things.
reworked plugins post-configuration (might drop it actually), now plugins are correctly initialized even if their global section is missing
cpufreqd 2.0.0-pre1 keywords