Hello, I noticed that with console-kit-daemon started, each time I switch to another console, it writes its state to disk. This limits a lot the possibility to save laptop power while e.g. reading documentation over several consoles. Couldn't consolekit rather write its status to a memory-backed FS, like /lib/init/rw? Samuel
tags 544483 wontfix thanks Samuel Thibault wrote: It's a log file which is meant to be kept during reboots (and e.g. used by ck-history) so writing to a tmpfs is not a good idea. The use case you are mentioning also sounds a bit artificial. Usually when you switch consoles you are triggering reads/writes anyway. Thus I'm marking the bug as wontfix Michael
Michael Biebl, le Tue 22 Sep 2009 23:23:01 +0200, a écrit : What for? Can that somehow be disabled? ?!?! I'm very often reading documents or source code in the train, and for that no read/writes are needed once everything is in cache. Samuel
tags 544483 - wontfix retitle 544483 Please give a way to disable console-kit-daemon startup reassign 544483 hal thanks Hello, My original concern is that "with console-kit-daemon started, each time I switch to another console, it writes its state to disk. This limits a lot the possibility to save laptop power while e.g. reading documentation over several consoles." Apparently, this is a feature of console-kit-daemon and will not be disabled. I have found that it's hal which starts console-kit-daemon, but I failed to find where that could be disabled. Is there one (and should thus be documented), or could it be added? Samuel
reassign 544483 dbus thanks Oops, it's not actually hal but dbus which is at stake. Hello, My original concern is that "with console-kit-daemon started, each time I switch to another console, it writes its state to disk. This limits a lot the possibility to save laptop power while e.g. reading documentation over several consoles." Apparently, this is a feature of console-kit-daemon and will not be disabled. I have found that it's dbus which starts console-kit-daemon, but I failed to find where that could be disabled. Is there one (and should thus be documented), or could it be added? Samuel
Samuel Thibault wrote: This feature is called dbus system activation [1]. I don't know of a documented way to disable a dbus activated service besides removing its service file from /usr/share/dbus-1/system-services. This obviously won't survive a package upgrade. As dbus follows the xdg spec, you might wanna try to copy the service file to /usr/local/share/dbus-1/system-services/ and set Exec=/bin/false This is an ugly hack though, so beware. Michael [1] http://kkaempf.blogspot.com/2009/03/d-bus-service-on-demand.html