>> > On Tuesday 01 August 2006 16:42, Joachim Schrod wrote:
>> >> Dave Cotton wrote:
>> >> > ...
>> >> >
>> >> > # At which time cron.daily should start. Default is 15 minutes
>> >> > after booting # the system. Due the cron script runs only every
>> >> > 15 minutes, it will only # run on xx:00, xx:15, xx:30, xx:45,
>> >> > not at the accurate time you set. DAILY_TIME="04:00"
>> >> AFAIR, the OP asked for 10.0 -- this sysconfig variable is new in
>> >> 10.1.
> I'm sure that when I added that control parameter to my
> my /etc/sysconfig/cron file that the next two days (all that have
> passed, so far) the Beagle indexing has happened at 4:00 AM as I
This interested me, and I tried it out. While the variable may move the beagle
indexing (I don't use beagle, so I didn't check that), it does definitively
*not* move the cron.daily jobs on a fully patched 10.0 system:
The day before yesterday, I changed cron.daily to run at 12:00.
Then, yesterday, I added this variable to /etc/sysconfig/cron:
On Mon, Jul 31, 2006 at 10:18:08AM +0800, 张韡武 wrote:
> Hello. I have an X terminal server ... as perhaps everybody already
> knows because I keep asking stupid questions... Sometimes beagled and
> its related process (e.g. parse-metadata) suddenly come up and take
> everybody by surprise by taking 100% CPU resource and slowing everything
> down. This keeps 10 minutes and everybody decide to get a coffee.
> Usually every user's beagled process start together.
parse-metadata is part of ZMD/zypp however, not beagle.