Re: how beagled is scheduled to run?

[Joachim Schrod]

Randall R Schulz wrote:

>> > 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
> indicated.

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:

     puma:/etc/sysconfig # grep DAILY cron
     DAILY_TIME="04:15"
     puma:/etc/sysconfig # ll cron
     -rw-r--r--  1 root root 2663 Aug  4 11:31 cron

But, the cron job still runs at 12:00 and has not been rescheduled to 04:15:

     puma:/etc/sysconfig # ll /var/spool/cron/lastrun/
     total 0
     -rw-r--r--  1 root root 0 Aug  4 12:00 cron.daily
     puma:/etc/sysconfig # date
     Sat Aug  5 10:21:25 CEST 2006

Therefore, this solution might work for beagle, but it is not a general
cron.daily reschedule solution on 10.0 -- only on 10.1.

Best,
        Joachim

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Joachim Schrod Email: [hidden email]
Roedermark, Germany

--
Check the headers for your unsubscription address
For additional commands send e-mail to [hidden email]
Also check the archives at http://lists.suse.com
Please read the FAQs: [hidden email]

[Marcus Meissner]

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.

Ciao, Marcus

--
Check the headers for your unsubscription address
For additional commands send e-mail to [hidden email]
Also check the archives at http://lists.suse.com
Please read the FAQs: [hidden email]