[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] Hook job classad stdin?
- Date: Thu, 12 Oct 2017 14:11:39 -0500
- From: Todd Tannenbaum <tannenba@xxxxxxxxxxx>
- Subject: Re: [HTCondor-users] Hook job classad stdin?
On 10/12/2017 1:56 PM, Michael Pelletier wrote:
It appears that the job ClassAd fed to the update job info hook doesn't include updates I had previously made with chirp. How is the hook input derived?
Basically what I'm trying to do is to get an expanded version of the input's classad, so that I can compare old values to avoid chirping something that hasn't changed. I'm dumping the stdin to a file and then running it through condor_q -jobads with an -af:lng and a list of all the attributes it found.
I know this is not answering your question (I am not Mr. Job Info Hook),
but I can tell you that there is practically no overhead involved in
doing a condor_chirp set_job_attr_delayed command. In other words, if
you can chirp with set_job_attr_delayed instead of set_job_attr, I
wouldn't worry optimizing to avoid re-chirping things that have not
Hope the above helps