gcc <email address hidden>:
> On our first Gutsy system I discovered trackerd eating 100% cpu... by
> sitting in a loop of continuous SIGSEGV. Catching SIGSEGV is usually a
> bad idea, and then reinstalling the signal handler is even worse. Please
> fix that.
I had the same experience. trackerd is a nasty hog, and it's a pain
having to kill it every time I boot. Even turning off every coverage
option I can find doesn't stop it from overwhelming my CPU -- and the
fact that I can't find whatever way there may be to disable it is
itself a bug.
gcc <email address hidden>:
> On our first Gutsy system I discovered trackerd eating 100% cpu... by
> sitting in a loop of continuous SIGSEGV. Catching SIGSEGV is usually a
> bad idea, and then reinstalling the signal handler is even worse. Please
> fix that.
I had the same experience. trackerd is a nasty hog, and it's a pain
having to kill it every time I boot. Even turning off every coverage
option I can find doesn't stop it from overwhelming my CPU -- and the
fact that I can't find whatever way there may be to disable it is
itself a bug.
Yes, this is under 7.10 kept current. www.catb. org/~esr/">Eric S. Raymond</a>
--
<a href="http://