|
Bugzilla – Full Text Bug Listing |
| Summary: | kerry: cannot stop beagled once it is started | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Forgotten User ZhJd0F0L3x <forgotten_ZhJd0F0L3x> |
| Component: | KDE | Assignee: | Joe Shaw <joeshaw> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | aj, joe, kukuk |
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Component Test | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | |||
| Bug Blocks: | 140732 | ||
|
Description
Forgotten User ZhJd0F0L3x
2006-02-02 11:14:56 UTC
Why do you want to stop it at all? You don't want to have a current index when using Beagle? (In reply to comment #1) > Why do you want to stop it at all? 2 reasons: ---------- - after e.g. synchronizing my IMAP mailbox, beagle causes ~60 seconds of 100%CPU and lots of disk activity - memory usage: seife@strolchi:~> ps aux|grep beagled seife 12190 2.3 8.6 189256 89128 ? Sl Feb01 22:25 mono-beagled --debug /usr/lib/beagle/BeagleDaemon.exe --fg seife 16612 1.4 2.7 74308 28820 ? Sl 13:00 0:32 mono-beagled-helper --debug /usr/lib/beagle/IndexHelper.exe > You don't want to have a current index when using Beagle? Of course, but sometimes i need my battery to last more than 60 minutes, and sometimes my machine needs to do something else than generation an index, something useful for example. > so file a beagle enhancement bug to pause if you're on battery? how does this help memory consumption? Add a .desktop file on your desktop/panel which executes 'beagle-shutdown'. :-) (In reply to comment #5) > Add a .desktop file on your desktop/panel which executes 'beagle-shutdown'. :-) Hm. "Enterprise Ready". NOT. Now runs beagle-shutdown on requested quit. There is no proper way in 10.1 rc1 to stop beagles indexing funcition. beagle-shutdown ERROR: The Beagle daemon does not appear to be running top shows me beaglein with 40-100% CPU consumption. If you remeber: one reason, why locate and updatedb was removed from the standard installation were the many user complaints about "Why is my harddrive working all the time if I start my system". Now with beagle in 10.1 rc1 it's the same. The user clients cannot stop it as this stuff is running as user beagleindex. I'm confused. Are we talking about beagle-build-index (the cron.daily job that runs as beagleindex) or the beagle daemon (the daemon that's started at login that runs as the user)? If we're talking about the cronjob, I had set it as a job to run at 4 am, but then I got bugs filed about *that* because it wasn't LSB compliant, so I switched it back to cron.daily which just runs whenever it wants to. *That* is the bug, IMO; cron.daily should be a lot smarter about when it runs its jobs. Either way, the cron job runs at nice +19 and IO priority idle, so it's as unobtrusive as possible. Unlike updatedb, beagle-build-index is incremental, so while there is a bit of a cost the very first time you run it, it's substantially lower in subsequent runs. What we need to do is stop running it 15 minutes after you boot your computer for the first time. The original report was about beagle daemon, comment 8 highjacked it for beagle-build-index. :-| Ok, this bug has lost focus. :) Why was it assigned to me? Is it for an enhancement request to pause the daemon when on battery? (also filed upstream as http://bugzilla.gnome.org/show_bug.cgi?id=325160) Is it an enhancement request for Kerry to be able to shut down the daemon? Is it to reduce memory usage, which is an ongoing thing upstream? I believe it is an enhancement request for Kerry to be able to shut down the daemon. A 'Stop Indexing' button if you'd like. Just my 2ยข. > Ok, this bug has lost focus.
Right. Marcel, please file a separate report for this and tell exactly what you want.
|