Knut Auvor Grythe wrote: > On Mon, Sep 12, 2005 at 12:09:19PM -0600, Ed Brown wrote: > > I appreciate your effort to clarify the algorithms involved in > > actionsequence scheduling, but even the algorithms don't explain the > > actual behavior very fully. > > It's actually quite simple. When you add "shellcommands.pre" to your > actionsequence, it means that "pre" is going to be defined when the > shellcommands sequence is run. This means that you need to test for > "pre" to know whether you are in that particular run of > shellcommands or > not. It behaves exactly like any other class.
And just to reinforce, the reason you don't see "any" printed out more than once in your examples is because of cfengine's locking mechanism, which declines to run the shellcommand "echo any" more than once per timeout. --Joe _______________________________________________ Help-cfengine mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-cfengine
