Hi, Could someone please tell me what are the differences between powersaved and acpid (for Suse 9.1) and why should I prefer one over another? I am getting troubled with powersaved going into some kind of zombie state where I have to kill and restart it every once a so often. So, I am considering trying acpid and was wondering if I would loose/gain any functionality. thanks, -- Osho
Am Donnerstag, 11. November 2004 22:37 schrieb Osho GG:
Hi,
Could someone please tell me what are the differences between powersaved and acpid (for Suse 9.1)
The difference ist that powersaved has more configuration possibilities (i.e. YaST Powersave module or editing configuration with the YaST etc/sysconfig Editor). And by the way: powersaved starts among other things acpid. Kind regars Siegfried
On Fri, 12 Nov 2004 05:41:11 +0100, Siegfried Heim
Am Donnerstag, 11. November 2004 22:37 schrieb Osho GG:
Hi,
Could someone please tell me what are the differences between powersaved and acpid (for Suse 9.1)
The difference ist that powersaved has more configuration possibilities (i.e. YaST Powersave module or editing configuration with the YaST etc/sysconfig Editor). And by the way: powersaved starts among other things acpid.
Hmm.. I thought powersaved or acpid were both exclusive to each othere.. Here is what I get: % ps -aef | grep powersave root 10222 1 0 20:15 ? 00:00:08 /usr/sbin/powersaved -d -e /etc/powersave.conf -a resmgr -v 3 % ps -aef | grep acpi root 5 3 0 Nov03 ? 00:01:11 [kacpid] I also checked in the run-level editor and it shows that powersaved service is enabled but acpid is disabled. Correct me if this this wrong. Thanks. -- Osho
On Fri, Nov 12, 2004 at 05:41:11AM +0100, Siegfried Heim wrote:
Am Donnerstag, 11. November 2004 22:37 schrieb Osho GG:
Hi,
Could someone please tell me what are the differences between powersaved and acpid (for Suse 9.1)
The difference ist that powersaved has more configuration possibilities (i.e. YaST Powersave module or editing configuration with the YaST etc/sysconfig
no. Powersaved has handling for acpi events and cpufrequency scaling integrated. It is also supposed to work on APM machines. Powersaved provides userspace preparation and handling for suspend and resume, acpid doesn't (but it can be made to handle this stuff also). There is a frontend for controlling powersaved as user from KDE. acpid only handles acpi events.
Editor). And by the way: powersaved starts among other things acpid.
only the 9.2 version and only to accomodate old programs still relying on the acpid socket. Btw: this compatibility mode can be switched off. -- Stefan Seyfried
Osho GG writes:
I am getting troubled with powersaved going into some kind of zombie state where I have to kill and restart it every once a so often.
What does that mean -- what are the symptoms of this zombie state? And do
you just kill and restart the daemon?
-K
--
Kevin Pfeiffer
On Fri, 12 Nov 2004 06:02:42 +0100, Kevin Pfeiffer
Osho GG writes:
I am getting troubled with powersaved going into some kind of zombie state where I have to kill and restart it every once a so often.
What does that mean -- what are the symptoms of this zombie state? And do you just kill and restart the daemon?
Sometimes after resuming, I notice that cpu throttling etc. powersave functions are not working. This seems to be because powersaved is running but seems to be "stuck" somehow. This can be easily seen by doing powersave -c This normally gives either PERFORMANCE or DYNAMIC as output - if powersaved is working properly. When, powersaved hangs powersave -c does not output anything and does not terminate. In this case, cpu throttling etc. also stops working. I have to do pkill -9 powresaved usr/sbin/rcpowersaved restart And, then things are working back to normal. -- Osho
participants (4)
-
Kevin Pfeiffer -
Osho GG -
Siegfried Heim -
Stefan Seyfried