Hi,

On 3/28/07, Boyd Lynn Gerber <[EMAIL PROTECTED]> wrote:
My main issue is that I can not get it to run only on off hours.  When it
is running I am unable to use my machine for anything worth while.  It
hogs most memory and CPU usuage.  I have problems with even the CLI.

There's an important distinction to be made here, and I'd like to know
which of these (or both) are biting you.  The more resource-intensive
indexing process is broken into two parts:

(a) A systemwide crawler which is run from cron.  This is very much
like the updatedb process you have if you install findutils-locate or
use another distribution like Fedora or Ubuntu.  This is used to index
systemwide resources like application launchers and system
documentation.  This is a one-off process run once a day.  This
process is called "beagle-build-index" in "ps ax" and is run from the
"beagle-crawl-system" cronjob.

(b) A per-user component which crawls your home directory and indexes
your personal data.  This (unless configured otherwise) stays within
your home dir and notices changes, additions, and removals in real
time.  This process exists for only as long as you are logged in.
These processes are called "beagled" and "beagled-helper" when you do
a "ps ax".

Right now (a) kicks off roughly every 24 hours.  The problem is that
it starts 15 minutes after you first installed the distro, so it often
runs right in the middle of your day!  This is very inconvenient, and
I mentioned that elsewhere in the thread.  Fortunately you can fix
this by editing the /etc/sysconfig/cron file and set the DAILY_TIME
variable to something like "04:00" to run at 4am.  After editing this
file, be sure to run "SuSEconfig".

For (b), it's the core component of Beagle and you can't turn it off
without turning search off altogether.  But (b) is also designed to be
as unobtrusive as possible, and so if it's eating your machine, it's a
bug and we need to track down why.

The problem is how do you attempt to debug it when you can not even do CLI
while it is running.  For example if I ssh to the box running beagle...  I
am unable to get a connection.  I am unable to mount or unmount a NFS
share from the machine.  Only when beagle is running.

Install the 0.2.16.3 version I mentioned earlier in the thread.
First, it may have fixed the bug you were seeing in the first place.
Secondly, if it didn't, it now runs at a higher "nice" level so
interactivity should improve even if it does run away.  And lastly,
you can disable it running at login time and run it in the foreground
and lots of debugging info with the "--fg --debug" options.  Hopefully
that will at least give you the opportunity to see what's going on and
more importantly to kill it if need be.

Thanks,
Joe
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to