Re: Executing once only

[Mark . Burgess]

On 15 Aug, Eric Sorenson wrote:
> On Fri, 15 Aug 2003 Mark.Burgess@iu.hio.no wrote:
> 
>> The ifelapsed and expireafter locks can now be placed as options
>> to every command individually, with global values as defaults. This
>> means that you can just set a very long ifelapsed and expire time
>> on the action, e.g. 9999 minutes which is effectively the same
>> as doing it once.
>> 
>> After that, if you are still worried about it timing-out, there
>> is ample time to comment out the rule.
> 
> You might want to leave it uncommented so new hosts will get the
> action once, but 9999 minutes is not the same thing as doing it
> once, it's only six days.  How about checking for '-1' and using
> that as the run-once determinant? 
> 

I think you are being unreasonable.

- What is the point of not commenting out a rule that might be dangerous.
  You want to live dangerously?

  9999 is seven days, so 999999999 is a very long time -- longer than
  you will be responsible for the job! And longer than the lifetime of
  your hosts.

I don't see the problem, and there is no sense in using -1 as a value.
That means nothing. Don't make things harder than they need be!!

M

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Work: +47 22453272            Email:  Mark.Burgess@iu.hio.no
Fax : +47 22453205            WWW  :  http://www.iu.hio.no/~mark
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~