Bug 147943

Summary:	beagle cronjob doesn't use cron.daily
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Dirk Mueller <dmueller>
Component:	GNOME	Assignee:	Joe Shaw <joeshaw>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Beta 3
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Dirk Mueller 2006-02-03 11:08:51 UTC

there is a beagle-crawl-system crontab in /etc/cron.d that doesn't belong there. it should be in /etc/cron.daily instead because this is the place where daily cron's are configured. 

otherwise the cronjob isn't restarted when the system wasn't running at 04:30am.

Comment 1 Gary Ekker 2006-02-03 17:31:15 UTC

We deliberately moved this from /etc/cron.daily to /etc/cron.d. This was because of how processor intensive it is.

Assigning to Joe to see if anything has changed here, to allow us to move it back to cron.daily.

Comment 2 Dirk Mueller 2006-02-03 17:37:21 UTC

90% of the machines you target for don't run all the night, and we don't use anachron. if you don't put it into cron.daily (or cron.weekly), it won't get run reliably. 

and if cpu usage is a problem, then fix it. Or see the other problem with the missing ionice (which is another bug).

Comment 3 Joe Shaw 2006-02-03 18:16:46 UTC

It's not processor usage so much as it's disk usage.  Users were filing bugs because it would start shortly after the system was booted.  This is also a problem for updatedb:

https://bugzilla.novell.com/show_bug.cgi?id=105922

Suggest we close this WONTFIX, or reopen the above bug and mark this as a dependency.

Comment 4 Dirk Mueller 2006-02-03 18:22:26 UTC

read bug 147944

Comment 5 Joe Shaw 2006-02-03 18:27:08 UTC

beagle used to set its own ionice (to a lower priority), but I guess that became a root-only thing at some point.

Comment 6 Dirk Mueller 2006-02-03 18:33:37 UTC

just set the ionice before you drop privileges..

Comment 7 Joe Shaw 2006-02-03 19:02:54 UTC

Yeah, we can do that for the cron job, but it seems from bug 147944 that shouldn't be necessary (it should inherit?) and we can't do it for the per-user daemon, which is where it really hurts performance.

Comment 8 Bryce Nesbitt 2006-02-13 20:39:28 UTC

Suggest you make Beagle off by default!

Comment 9 Joe Shaw 2006-04-06 22:09:15 UTC

Switched back to using cron.daily, and added a patch to speed up the crawl (especially on incremental updates) tremendously.  Submitted to STABLE.