From: Grover, Andrew <andrew.grover@in...> - 2003-03-27 02:24:37
> From: S=E9rgio Monteiro Basto [mailto:sergiomb@...]=20
> and talking about ospmd, yes, it never worked, we have a=20
> missing config
> file that make GUI doens't work, and in this case I never knew about =
> basic example...=20
> Normally is the thing that is missed on every man and help pages of
> Linux :)=20
OK so here's the deal with ospmd:
It works. On my RH 8 machine. ;-) Specifically, the qt include path is
hardcoded in the gui Makefile. Bad, bad, I know. But look, the raw =
of what I envision for a power policy daemon and power library are =
- ospmd handles *both* ACPI and APM kernel interfaces, and presents a
uniform PM interface. Other PM interfaces could be easily supported, =
- ospmd creates a config file with default values, and these can be =
in the .conf file (/var/ospmd.conf) or can be set via libpower.
- libpower presents a rich, uniform interface for power applets to use.
Power policy is centralized, so changes made through a kde and gnome =
(for example) both affect the same policy. Applets and battery meters =
longer have to parse /proc, or perform battery life calculations - =
- further enhancements could include APIs for apps to request that the
screen not be blanked (e.g. presentation apps) or to keep the system =
suspend (e.g. cd writing apps).
I really believe strongly that ospmd (or something like it) will be the =
to go for a standard PM policy daemon and interface in the future. I am
frustrated that ACPI kernel issues and other work have prevented me =
productionalizing it with man pages, better build system, better test =
etc. but I think this will be a very important part of a modern =
power management architecture.
Regards -- Andy