Comment 3 for bug 400863

Reopening bug. Even with the logrotate file in place, and having verified that log rotation *has* occurred
ck-history still takes a prohibitively long time to run.

Indeed, now that some of the history is gzipped, ck-history is now up from taking 20 seconds to taking 40 seconds!

I have now realized that the reason one of my machines is so severely affected is because it has frequent cronjobs, causing the history to be extremely extensive.

I would like to propose that calling ck-history at all is rather unnecessary in the case of an average home user's desktop, where the number of non-system accounts will be very small.