[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] File last modification time or job last write() attribute?
- Date: Fri, 27 May 2016 05:47:41 +0000
- From: MIRON LIVNY <miron@xxxxxxxxxxx>
- Subject: Re: [HTCondor-users] File last modification time or job last write() attribute?
You are right, Dimitri.
The reason I used C was to make the point that the definition of "stuck" has an impact on the frequency of the probe. I can see cases where the probe is expensive.
In the case if all goes well we will probe in a very low frequency.
Sent from my iPhone
> On May 26, 2016, at 23:41, Dimitri Maziuk <dmaziuk@xxxxxxxxxxxxx> wrote:
>> On 05/26/2016 01:51 PM, MIRON LIVNY wrote:
>> We are making excellent progress!
>> Having to monitor just one file is good news.
>> My current understanding is that if at time T you observe that the
> file was updated at time U you would like to check the last update time
> of the file again at time C = U + 1 hour. If T > C you want to terminate
> the job.
> To me it sounds that if U < (T - 1 hour) the job is stuck.
> Dimitri Maziuk
> BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> The archives can be found at: