CPU consumed by /usr/sbin/update
Every so often (in increasingly short intervals) since getting Tiger I've noticed that a process called update begins to consume my CPU cycles and will never let them go.
The process update is found in /usr/sbin/update, and is run when the computer starts as it is "the daemon that flushes internal file system caches to disk frequently".
So my 7 day uptime (the last time was a week ago when my uptime was around 14 days) ends by having to force restart the computer. A simple restart will not suffice as the application I believe is hung and will not accept any kill signals. (So yes, sudo kill -9 will not work). Now I'm wondering, does anyone know why this could be happening?
Or is it just yet another graemlin in my hard drive causing this?
I still remember Macnutt.