Comment 16 for bug 400863

We have a Ubuntu 10.04 LTS machine set up in vmware for serving a git repository over ssh and our Hudson instance do several polls a minute.

This is how our /var/log/ConsoleKit looks:

root@Sandbox:/var/log/ConsoleKit# ls -l
total 457424
-rw-r--r-- 1 root root 228364612 2011-02-28 14:41 history
-rw-r--r-- 1 root root 210159903 2011-02-01 08:00 history.1
-rw-r--r-- 1 root root 12436950 2011-01-01 07:45 history.2.gz
-rw-r--r-- 1 root root 10235104 2010-12-01 07:46 history.3.gz
-rw-r--r-- 1 root root 6888399 2010-11-01 07:43 history.4.gz
-rw-r--r-- 1 root root 293954 2010-10-01 07:37 history.5.gz
-rw-r--r-- 1 root root 267 2010-09-14 15:56 history.6.gz
root@Sandbox:/var/log/ConsoleKit#

This has resulted in a load over 1 for the last couple of weeks as the vmware instance primarily is at the login screen, and I've just analyzed it and found that the culprit is ck-history with 99% cpu usage.

Is there any particular reason why fancy history parsing is necessary to provide a _server_ login screen?

How do I disable this behaviour?

Thanks in advance

/Thorbjørn Ravn Andersen