[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Structuring the cfagent for daily tasks
From: |
Mark . Burgess |
Subject: |
Re: Structuring the cfagent for daily tasks |
Date: |
Wed, 17 Apr 2002 11:09:20 +0200 (MET DST) |
On 17 Apr, Adrian Phillips wrote:
>>>>>> "Benny" == Benny Kjellgren <benny.kjellgren@genuity.se> writes:
>
> Benny> Hello. I have used the following way to perform daily
> Benny> tasks (cfagent.conf) :
>
> Benny> import: any:: cf.groups cf.site Hr00:: cf.site_daily
>
> Benny> I like this idea that cfagent do not parse daily tasks
> Benny> every time cfagent runs. But sometime I want to force a
> Benny> machine to do daily tasks (not Hr00).
>
> Benny> There is many ways to do this (I think) : -
> Benny> "Hr00|myclass_that_force::" Some file that is touched (or
> Benny> not) - some options to cfagent - design cf.site_daily
> Benny> autonomous and do 'cfagent -f cf.site_daily'
>
> Benny> Q: How to make daily tasks that can be forced ? And still
> Benny> have a nice structure.
>
> -D Hr00 (?)
>
> Sincerely,
>
> Adrian
>
Yes, you are both on the right track. I think that
Hr00|myclass_that_forces::
action
and cfagent -D myclass_that_forces is more elegant than forcing the time Hr00
(though this is possible). Forcing the time might have other consequences.
Mark
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Work: +47 22453272 Email: Mark.Burgess@iu.hio.no
Fax : +47 22453205 WWW : http://www.iu.hio.no/~mark
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~