[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] $RETRY variable in job definition?



Hi Kent,

Is the retry count in the ad at all?  It's something that would be really useful in my case.

Brian

On Nov 1, 2013, at 9:55 AM, R. Kent Wenger <wenger@xxxxxxxxxxx> wrote:

> On Fri, 1 Nov 2013, Brian Bockelman wrote:
> 
>> Seems that this would be easier (or at least better described in the manual)...
>> 
>> I'd like to have my output files saved for each retry of a dagman node. Currently, they are named:
>> 
>> out.1234
>> 
>> I'd like to make these unique per job attempt; i.e.,
>> 
>> out.1234.0
>> out.1234.1
>> 
>> etc.
>> 
>> Is there any way to do this?  If so, is there any way I could have figured this out from the manual?
> 
> Well, the easiest way would be to have a POST script something like this:
> 
> Script Post <node name> rename_out $RETRY
> 
> rename_out:
>  #!/bin/sh
>  mv out.1234 out.1234.$1
> 
> I guess there's no reason we couldn't make a $(RETRY) that can be used in a VARS specification, but that's not currently implemented.
> 
> Kent Wenger
> CHTC Team
> _______________________________________________
> 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/