[NTLUG:Discuss] The Beagle dog on SuSE

[Robert Pearson]

On Wed, Jan 28, 2009 at 7:30 PM, Leroy Tennison
<leroy_tennison at prodigy.net> wrote:
> Chris Cox wrote:
>> Leroy Tennison wrote:
>>> ... 10.3 to be exact.  Wondered why my machine was running dog slow.
>>> Thought I had killed off the hound some time back when we first had the
>>> Beagle discussion.  However, looked at the process table and there it
>>> was: beagled (and beagle-helper something).
>>
>> You can try removing all of the beagle packages... though there
>> may be some dependency conflicts in doing that (not sure).
>>
>> It usually stays dead when configured to be dead though...
>> at least from my own experience.
>>
>>> Went to Services in the GUI - no beagle listed.  Went to the init
>>> scripts under /etc, no obvious mutts there either.  Fortunately 'grep -R
>>> beagle *' at /etc surfaced at least one issue, SuSE had launched it via
>>> cron.  Created /etc/cron.never and moved the beagle script there, we'll
>>> see if I've fixed the problem and found all the culprits.
>>>
>>> Anybody know if SuSE has any other standard ways of launching this mongrel?
>>>
>>> This raises the question "Is there a way to prevent a daemon from
>>> running something akin to hosts.deny for disallowing access by various
>>> hosts?"
>>
>> _______________________________________________
>> http://www.ntlug.org/mailman/listinfo/discuss
>>
> Thanks for the points, it looks like I'm going to have to either remove
> the package, rename the executable or something (it was back tonight).
> After killing it again things were still slow.  'top' surfaced another
> culprit: zypper
>
> Now I've got to figure out what's causing it to run and decide whether I
> can do something about that.
>

Since I don't run SuSE anymore I have deleted all my howto's and
goby'a for fixing this.
A quick google revealed this fix:
===
Since I installed 10.3, I notice an awfull lot of disc activities
during the, say, five minutes following boot. I've suspected
beagle,but if I run top I see that the culprit seems to be "zypper". I
can't figure out what it's doing, but it's eating up to 97% of my CPU
time at moments.

I've done some search, but I am not sure if I could reduce zypper's
activity, or simply remove it? Seems to be used by Yast2 for package
management, but can Yast2 do without?

(Re: post from Yesterday)

Modifying this behavior is simple. Just right-click opensuseupdater in
the sys tray, choose quit and then click "do not start on login" (or
something similar). This will disable online update from running every
time you login and stop the automaitc refresh of all repositories.

This is no big deal, I run that way. Just remember you must manually
do the yast->online update once in a while.

Depending on whether you use Beagle search index, you will also want
to either (1) disable Beagle in control center, or (2) remove it
completely with "rpm -e $(rpm -qa | grep beagle) kerry" from the
command line as root.

After making those two modifications, you will not experience any more
slowdown during the first 5-10 minutes after login. Online update and
beagle are the problems.

For online update the solution is to configure
yast->software->configure online update. You can set online update to
run weekly/monthly, etc. That way you can still stay current on
updates without it running on every login.
http://linux.derkeiler.com/Mailing-Lists/SuSE/2008-01/msg02275.html
===