I wrote this Monit entry to try to bring console-kit-daemon under control, but it hasn't seemed to be effective, as the console-kit-daemon CPU use seems to fluctuate as it ramps up to seize all CPU. As this happens, I lose interactive control of my X session, even though running on a dual-CPU system.
check process console-kit-daemon with pidfile /var/run/console-kit-daemon.pid
start program = "/usr/bin/ck-launch-session"
stop program = "killall -9 console-kit-daemon"
if 5 restarts within 5 cycles then timeout
if cpu usage > 3% for 5 cycles then alert
I agree - the urgency of this is no less than HIGH, and needs quick attention.
I wrote this Monit entry to try to bring console-kit-daemon under control, but it hasn't seemed to be effective, as the console-kit-daemon CPU use seems to fluctuate as it ramps up to seize all CPU. As this happens, I lose interactive control of my X session, even though running on a dual-CPU system.
check process console-kit-daemon with pidfile /var/run/ console- kit-daemon. pid ck-launch- session"
start program = "/usr/bin/
stop program = "killall -9 console-kit-daemon"
if 5 restarts within 5 cycles then timeout
if cpu usage > 3% for 5 cycles then alert
I agree - the urgency of this is no less than HIGH, and needs quick attention.