Hi Holger,

first: thanks for updating the documentation, this is really needed :-)

On Thu, Dec 07, 2006 at 04:38:30PM -0700, Novell Forge SVN wrote:
 
> -The powersave daemon defines three battery states:
> +The powersave daemon defines three battery states. They will only be taken
> +into account if no other application caring about power management (such
> +as kpowersave or gnome-power-manager) is running.
 
> Modified: trunk/powersave/docs/README.buttons
> ===================================================================
> --- trunk/powersave/docs/README.buttons       2006-12-06 04:00:49 UTC (rev 
> 2733)
> +++ trunk/powersave/docs/README.buttons       2006-12-07 23:38:22 UTC (rev 
> 2734)
> @@ -1,3 +1,7 @@
> +These settings will only be taken into account if no other application
> +caring about power management (such as kpowersave or gnome-power-manager)
> +is running.

> Modified: trunk/powersave/docs/README.cpufreq
> ===================================================================
> --- trunk/powersave/docs/README.cpufreq       2006-12-06 04:00:49 UTC (rev 
> 2733)
> +++ trunk/powersave/docs/README.cpufreq       2006-12-07 23:38:22 UTC (rev 
> 2734)
> @@ -1,3 +1,7 @@
> +The Powersave Daemon will only care about CPU frequency scaling if no
> +other application caring about power management (such as kpowersave or
> +gnome-power-manager) is running.

> Modified: trunk/powersave/docs/README.internals
> ===================================================================
> --- trunk/powersave/docs/README.internals     2006-12-06 04:00:49 UTC (rev 
> 2733)
> +++ trunk/powersave/docs/README.internals     2006-12-07 23:38:22 UTC (rev 
> 2734)
> @@ -1,9 +1,9 @@
>       @section The Daemon
>  
> -     The heart of the package is the daemon (@code{/usr/sbin/powersaved}).
> -     It listens for client requests (normally from non-root users), listens
> -     for hardware changes and checks e.g. the CPU load to adjust the CPU
> -     frequency dynamically.
> +     The heart of the package is the daemon
> +     (@code{/usr/sbin/powersaved}).  It listens for hardware changes
> +     and checks e.g. the CPU load to adjust the CPU frequency
> +     dynamically.

Does it still do that?

> Modified: trunk/powersave/docs/README.schemes
> ===================================================================
> --- trunk/powersave/docs/README.schemes       2006-12-06 04:00:49 UTC (rev 
> 2733)
> +++ trunk/powersave/docs/README.schemes       2006-12-07 23:38:22 UTC (rev 
> 2734)
> @@ -1,3 +1,7 @@
> +     These settings will only be taken into account if no other application
> +     caring about power management (such as kpowersave or 
> gnome-power-manager)
> +     is running.

Generally this is not true. An application can care about it, but if it 
doesn't grab the DBus interface, it won't matter, or am i wrong?

So explaining somewhere what exactly (in technical terms) an application has
to do to count it as "caring about power management" would be good.

Thanks :-)

    Stefan
-- 
Stefan Seyfried                  \ "I didn't want to write for pay. I
QA / R&D Team Mobile Devices      \ wanted to be paid for what I write."
SUSE LINUX Products GmbH, Nürnberg \                    -- Leonard Cohen
_______________________________________________
powersave-devel mailing list
[email protected]
http://forge.novell.com/mailman/listinfo/powersave-devel

Reply via email to