cruelwei 发表于 2006-2-27 14:16:00

为什么 powersaved 不能自动启动?

请问ML中的powersaved怎么设置,为什么我每次在konsole起动了,也设置了ntsysv,每次重起后还要再设。。?

我现在在普通用户下,用Konsole进入root,然后启动了powersaved服务,在ntsysv里也设置了,并在root中启动了kpowersave,那个图标出现了,的确降频了,我也把kpowersave开机运行的选项也选上,(如果我在普通用户下打开kpowersave是无法进行设置?)这时我选择重新启动。重启之后进入,发现kpowersave并没有启动,在普通用户状态下(不进入root)打开kpowersave,依然无法设置,并且屏幕显示:
“powersave 守护进程没有运行。
启动此程序将提高性能:rcpowersaved start
可运行chkconfig powersaved on加到自启动服务中”
我用konsole查询
# service powersaved status
powersaved dead but pid file exists
这是为什么啊!?难道说我每次都要手动开一遍服务么?
这里有个帖子,其中一位朋友也是这种情况   http://www.linuxfans.org/nuke/modules.php?name=Forums&file=viewtopic&t=146394&sid=

以下是我的设定步骤, 是按照这里介绍进行设置的 http://mlwiki.maihaohui.com/index.php/Notebook/powersave
但是显示的不太一样。

# service powersaved start
Starting powersaved(accessing ACPI events over acpid)   
# kpowersave&
2743
# kpowersave
DCOPClient::attachInternal. Attach failed Could not open network socket
DCOPClient::attachInternal. Attach failed Could not open network socke
DCOPClient::attachInternal. Attach failed Could not open network socke
Link points to "/tmp/ksocket-root"
Link points to "/tmp/kde-root"
kbuildsycoca running...
KWrited - 在设备 /dev/pts/2 上监听
QString::arg(): Argument missing: ?????????
????? 30 ?? %s ??, 30
DCOPClient::attachInternal. Attach failed Could not open network socke
kdeinit: Shutting down running client.
---------------------------------
It looks like dcopserver is already running. If you are sure
that it is not already running, remove /root/.DCOPserver_ML__0
and start dcopserver again.
---------------------------------

KDE Daemon (kded) already running.
kbuildsycoca running...
Reusing existing ksycoca
kbuildsycoca: WARNING: '/usr/share/applications/net-gvim.desktop' spec
kbuildsycoca: WARNING: '/usr/share/applications/net-gvim.desktop' spec
kbuildsycoca: WARNING: '/usr/share/applications/net-gvim.desktop' spec
kbuildsycoca: WARNING: '/usr/share/applications/gimp-2.2.desktop' spec
kbuildsycoca: WARNING: '/usr/share/applications/gimp-2.2.desktop' spec
kbuildsycoca: WARNING: '/usr/share/applications/gimp-2.2.desktop' spec
kbuildsycoca: WARNING: '/usr/share/applications/gimp-2.2.desktop' spec
kbuildsycoca: WARNING: '/usr/share/applications/gimp-2.2.desktop' spec
kbuildsycoca: WARNING: '/usr/share/applications/gimp-2.2.desktop' spec
kbuildsycoca: WARNING: '/usr/share/applications/gimp-2.2.desktop' spec
kbuildsycoca: WARNING: '/usr/share/applications/gimp-2.2.desktop' spec
kbuildsycoca: WARNING: '/usr/share/applications/gimp-2.2.desktop' spec
kbuildsycoca: WARNING: '/usr/share/applications/gimp-2.2.desktop' spec
kbuildsycoca: WARNING: '/usr/share/applications/gimp-2.2.desktop' spec
kbuildsycoca: WARNING: '/usr/share/applications/gimp-2.2.desktop' spec
kbuildsycoca: WARNING: '/usr/share/applications/gimp-2.2.desktop' spec
kbuildsycoca: WARNING: '/usr/share/applications/gimp-2.2.desktop' spec
kbuildsycoca: WARNING: '/usr/share/applications/gimp-2.2.desktop' spec
kbuildsycoca: WARNING: '/usr/share/applications/gimp-2.2.desktop' spec
kbuildsycoca: WARNING: '/usr/share/applications/gimp-2.2.desktop' spec
kbuildsycoca: WARNING: '/usr/share/applications/wine.desktop' specifie
kbuildsycoca: WARNING: '/usr/share/applications/wine.desktop' specifie
kbuildsycoca: WARNING: '/usr/share/applications/wine.desktop' specifie
kbuildsycoca: WARNING: '/usr/share/applications/wine.desktop' specifie
kbuildsycoca: WARNING: '/usr/share/applications/wine.desktop' specifie
kbuildsycoca: WARNING: '/usr/share/applications/wine.desktop' specifie
kbuildsycoca: WARNING: '/usr/share/applications/wine.desktop' specifie
kbuildsycoca: WARNING: '/usr/share/applications/wine.desktop' specifie
kbuildsycoca: WARNING: '/usr/share/applications/wine.desktop' specifie
kbuildsycoca: WARNING: 'kcertpart.desktop' specifies undefined mimetyp
kbuildsycoca: WARNING: '/usr/share/applications/kde/kaffeine.desktop'
kbuildsycoca: WARNING: 'kaffeine_part.desktop' specifies undefined mim
kbuildsycoca: WARNING: 'kaffeine_part.desktop' specifies undefined mim
kbuildsycoca: WARNING: 'qeditor_part.desktop' specifies undefined mime
kbuildsycoca: WARNING: 'qeditor_part.desktop' specifies undefined mime
kbuildsycoca: WARNING: 'qeditor_part.desktop' specifies undefined mime
kbuildsycoca: WARNING: 'qeditor_part.desktop' specifies undefined mime
kbuildsycoca: WARNING: 'knotify.desktop' specifies undefined mimetype/
kbuildsycoca: WARNING: '/usr/share/applications/mplayer.desktop' speci
kbuildsycoca: WARNING: '/usr/share/applications/amarok.desktop' specif
KPowersave is already running!
+Done                  kpowersave



第一次启动kpowersave 是这样的,以后每次启动只有这个
Link points to "/tmp/ksocket-root"
Link points to "/tmp/kde-root"
kbuildsycoca running...
KWrited - 在设备 /dev/pts/2 上监听
QString::arg(): Argument missing: ?????????
????? 30 ?? %s ??, 30

KDE 发表于 2006-2-27 22:23:22

sorry,这是移植 powersaved 时引入的一个 BUG,由于 powersaved 依赖 HAL,我们没有注意到其启动顺序被放在了 HAL 前方,导致不能在启动时正常加载。修改方法:
编辑 powersaved 脚本:
kwrite /etc/rc.d/init.d/powersaved
修改 # chkconfig: 345 66 34为 # chkconfig: 345 99 01 并保存:

#!/bin/bash
# chkconfig: 345 66 34
# description: Powersave Daemon
# processname: powersaved

#!/bin/bash
# chkconfig: 345 99 01
# description: Powersave Daemon
# processname: powersaved

这是为了把启动顺序置于 haldaemon(98) 之后(99),而关闭顺序置于 haldaemon(02) 之前(01)。也可以使用图形用户界面的 SysV init 编辑器修改(在系统菜单里)。

然后执行:
chkconfig --level 2345 powersaved on
在 2-5 四个运行级启动 powersaved,最后运行:
service powersaved start
立即启动 powersaved 服务,此时您会看到:
Starting powersaved(accessing ACPI events over acpid)    [OK]

最后在系统菜单里选择 kpowersaved 启动电源管理工具即可。为了使普通用户也能正常执行 kpowersaved,你需要编辑 /etc/sudoers,例如你的用户名是 athena,在 athena 为首的一行添加 kpowersave 命令:

athena ALL=NOPASSWD:/bin/mount -t iso9660 -o loop\,ro\,nodev\,exec\,nosuid\,* */Mount-ISO*,/bin/umount */Mount-ISO*,/usr/sbin/adsl-connect,/usr/sbin/adsl-start,/usr/sbin/adsl-status,/usr/sbin/adsl-stop,/usr/bin/kpowersave

注意命令之间用逗号隔开。

jozhu 发表于 2006-3-6 09:07:03

楼上的方法试了,没有作用阿。

KDE 发表于 2006-3-9 02:45:00

什么叫没有作用?是服务没有启动,还是启动服务后 CPU 不能降频?

jozhu 发表于 2006-3-28 07:38:06

服务没有启动啊

jozhu 发表于 2006-3-28 07:38:51

“powersave 守护进程没有运行。
启动此程序将提高性能:rcpowersaved start
可运行chkconfig powersaved on加到自启动服务中”

这几行依旧存在
页: [1]
查看完整版本: 为什么 powersaved 不能自动启动?