Hi, On 7/6/07, Bob Kline <bkline@rksystems.com> wrote:
Click on the "Service" tab. You should see beagled there chewing up your resources like old bones.
Kill it by clicking disable.
I had looked there, but it apparently hadn't been running as a service, as it didn't show up in the list of services.
Yeah, it won't show up there because it's a per-user service (like D-BUS or gnome-session or kinit) and not a system-wide one. There are different ways to enable or disable startup programs depending on whether you're running GNOME or KDE.
De select (if selected) beagle, beagle-gui and kio-beagle. That should get rid of the cursed beast forever from your system, which will now increase in performance threefold.
Well, I had done that (as I thought I had tried to convey in my original post), but although those beagle packages were gone, the beagled-helper process was still running. I finally got desperate and just killed it.
beagle-shutdown will shut down both the main daemon process (beagled) and the indexer (beagled-helper). But if you're not interested in running it, killing it is fine. You'll probably also want to delete ~/.beagle, as that's where the indexes are stored. If beagled-helper was stuck, that's a bug that's likely fixed, and an update might help.
Don't think I've ever come across a package manager (outside of MS Windows, that is) which didn't stop the processes belonging to a package being removed. Strange.
It's fairly common for RPM not to kill per-user processes, and I don't really know what the SUSE packaging policy is for this. You might want to file a bug and I'll look into fixing it. Thanks, Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org