Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] Preserve history in classad expression
- Date: Mon, 23 Sep 2019 20:24:03 -0400
- From: Jose Caballero <jcaballero.hep@xxxxxxxxx>
- Subject: Re: [HTCondor-users] Preserve history in classad expression
Hi Marco,
AFK, so from the top of my head, would it help to check for UNDEFINED in the logic ?
Good luck,
Jose
On Sep 23, 2019, at 18:31, Marco Mambelli <marcom@xxxxxxxx> wrote:
> Greetings,
> I was wondering if there is a way to use the last value of an attribute evaluation to calculate the next one in a classad.
> Let's say I'd like to have a trigger that trips a switch that remains set for the rest of the life of the machine (until it's killed or there is a restart).
> Something like a circuit breaker.
> Is that possible? How could I do that?
>
> Something like this in the configuration is not working:
> MYSWITCH = false
> MYSWITCH = $(MYSWITCH) || MYTRIGGER
>
> In each evaluation the switch is reset to false, then the result will be true only while the trigger is true, not preserved later.
>
>
> I tried also to have the value in the log file using the debug macro:
> MYSWITCH =debug( $(MYSWITCH) || MYTRIGGER)
> but I did not see anything in the log files. The switch value is used in the start expression, so it should be evaluated periodically.
>
>
> Thanks,
> Marco
>
>
>
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
>
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/