Carl Lowenstein wrote: > On 1/29/07, Serge Rey <[EMAIL PROTECTED]> wrote: >> On Mon, Jan 29, 2007 at 12:26:43PM -0800, Carl Lowenstein wrote: >> > This morning I looked in at my Thinkpad T30 (1.8GHz P4M) after it had >> > been running a screensaver all night, and found that everything >> > user-interactive had slowed to a crawl. >> > >> carl, >> >> did you turn these services on yourself, or were they set up out of >> the box? >> the reason i ask is i'm running a fresh fedora core 6 install on a >> desktop and >> don't see those guys running. > > Fresh out of the box. Note that all but yum-updatesd are started from > cron.daily. So I can reduce the average impact by moving them to > cron.weekly. > > But I still don't understand why several of these services should be > thrashing the disk simultaneously. I haven't yet looked into > run-parts which is what actually sequences them.
Well, you've probably already looked and found that run-parts simply runs all executables (with some fancy qualifications) in the directory it's told to use .. .. by /etc/crontab If you want to split things out of cron.daily (which _all_ run at the same time, then you would have to separately schedule them. The cron.daily is a neat idea for most things -- but evidently not all. Perhaps beagle should be separately scheduled -- look into /etc/cron.d for other utils that set their own preferred times. Or, perhaps you've been hit by either: - a one-time occurrence of initial runs (eg, beagle?) - a hw/sw bug, where something is retrying forever? Regards, ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
