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

Re: [HTCondor-users] File last modification time or job last write() attribute?

Keep in mind if you use inotify you will definitely have to increase the number of watches available... and you still will probably run out after awhile.

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> on behalf of Iain Bradford Steers <iain.steers@xxxxxxx>
Sent: Wednesday, May 25, 2016 1:07:45 PM
To: HTCondor-Users Mail List
Subject: Re: [HTCondor-users] File last modification time or job last write() attribute?
There’s also a delayed set available via the condor_chirp utility.

Gets back to the schedd with a maximum of 15-minutes delay IIRC.

Cheers, Iain

On May 25, 2016, at 19:58, Michael V Pelletier <Michael.V.Pelletier@xxxxxxxxxxxx> wrote:

From: Iain Bradford Steers <iain.steers@xxxxxxx>
Date: 05/25/2016 01:37 PM

> Hi Michael,
> I’m not aware of an existing classad attr that gives that information.

> In theory condor_chirp could be used to update a timestamp of the last
> file write to those files.

> Scalability would have me concerned but perhaps you could register an
> inotify watcher in the user_job_wrapper and have a condor_chirp call as
> part of the inotify callback.

> Cheers, Iain

The inotify idea is interesting, though I would definitely see scalability
challenges with that approach. Wouldn't want to chirp on every write, that's
for sure. The 5-minute interval of the update_job_info hook seems
like it would address scalability concerns but still keep enough
granularity to make the data useful in expressions. But being able to do
it without occupying the HookKeyword would be handy too.

Thanks for the suggestion!

        -Michael Pelletier. _______________________________________________
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: