ConsoleKit manages console logins in graphical mode (i.e. with gdm or equivalent), if you don't need it, you can kill easily and free your memory and cpu usage.Sound like you run graphical env... is true?
–
PersianGulfMar 20 '13 at 18:55

@Mohsen Yes, and unfortunately it's a requirement for the primary user, so I can't just kill ConsoleKit. I was thinking it might be a version issue, but we're pretty close to being completely up to date; I've just run out of ideas to try.
–
Michael ToddMar 20 '13 at 19:00

@Sukminder That displays a list of 63 lines, I'm assuming threads, associated with console-kit. I have a feeling that these threads are getting started and not shut down properly (hence the memory use). Any suggestions as to how to do that other than manually killing them?
–
Michael ToddMar 20 '13 at 20:37

2 Answers
2

Kill the console-kit-daemon process if it's still running.
Remove the file /usr/share/dbus-1/system-service /org.freedesktop.ConsoleKit.service (or move it to some place where you could restore it, if necessary).
Reboot and you will see that console-kit-daemon no longer automatically starts up.