Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 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? Commented Mar 20, 2013 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. Commented Mar 20, 2013 at 19:00
  • Perhaps htop in tree mode (F5) can give more info? Or even pstree -pacs PID ... Commented Mar 20, 2013 at 20:33
  • @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? Commented Mar 20, 2013 at 20:37
  • No. I don't know. Hopefully someone do. Only had a quick peek at bugzilla.redhat.com/show_bug.cgi?id=473547#c44 , bugs.freedesktop.org/show_bug.cgi?id=17720#c17 and the like ... - Perhaps Mr. Poettering has a web-alert on console-kit :P Commented Mar 20, 2013 at 21:12