From: "Jürgen Geuter" <tante@emptiness.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Beagle eating up Resources!! (BEagled-index-helper)
Date: Tue, 27 Feb 2007 13:06:28 +0100 [thread overview]
Message-ID: <1172577988.7233.13.camel@yatahaze.skynet.local> (raw)
In-Reply-To: <1172570953.32328.104.camel@neuromancer.home.net>
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
On Tue, 2007-02-27 at 18:09 +0800, Ow Mun Heng wrote:
> Does anyone here knows if beagle really sucks up resources?? I just
> emerged it a week ago and I'm getting very pissed off at it as it's
> using a lot of resources. The laptop doesn't get much idle time.
Beagle is quite a resource hog and will keep your system busy whenever
it finds it to be "idle", that is the reason why I decided to ditch it
(I wasn't using the search functionality that much anyways).
You could make sure that "beagled" is not started upon login, that way
it will not do autoscanning of your files and only start when you use
it.
regards
Jürgen
--
ICQ #81510866 - http://the-gay-bar.com - MSN tante@emptiness.de
Occam's Razor:
-"Entia non sunt multiplicanda praeter necessitatem."-
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-02-27 12:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 10:09 [gentoo-user] Beagle eating up Resources!! (BEagled-index-helper) Ow Mun Heng
2007-02-27 12:06 ` Jürgen Geuter [this message]
2007-02-27 13:21 ` Kristian Poul Herkild
2007-02-27 13:41 ` Jürgen Geuter
2007-02-28 9:30 ` Ow Mun Heng
2007-02-28 21:28 ` Roy Wright
2007-02-28 23:50 ` Kent Fredric
2007-03-01 0:26 ` Albert Hopkins
2007-03-01 0:54 ` Ow Mun Heng
2007-03-01 14:10 ` Roger Mason
2007-03-04 1:16 ` Alan E. Davis
2007-02-27 13:18 ` Kristian Poul Herkild
2007-02-28 22:25 ` Matthias Bethke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1172577988.7233.13.camel@yatahaze.skynet.local \
--to=tante@emptiness.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox