Re: Possible bug: parsing/scheduling of editfiles sections in multiple cfengine scripts

[Knut Auvor Grythe]

On Mon, Sep 12, 2005 at 03:25:47PM -0500, Brendan Strejcek wrote:
>> So what you need to do is have a proper way of checking what
>> shellcommands run you are in. If you have the actionsequence (
>> shellcommands.foo shellcommands.bar ), you need to test for foo and
>> bar to know which run you are in. If you don't test for them, then
>> the command will run both times. This makes sense, because you are
>> basically saying "i don't care when it runs".
> 
> In general I think this is true, but won't locking prevent the same
> command from running twice?

Why would it? I certainly hope locks are released when the program
associated with it finishes. If you configure something to run in each
run of shellcommands, it should run in each run of shellcommands.
Anything else would be a serious bug.

-- 
Knut Auvor Grythe
ITEA Systemdrift