[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] Updating Job ClassAd during job run
- Date: Fri, 04 Mar 2022 14:10:19 -0800
- From: Matthew Ens <mfens98@xxxxxxx>
- Subject: Re: [HTCondor-users] Updating Job ClassAd during job run
Unfortunately I don't think any of these options will work for us as we
operate our HTCondor for the WLCG and get jobs from several different
places we cannot update the job submit file. Also, reading about option
(3) there might be some misunderstanding, we want to run a script in
the job wrapper and use the output of the script to update the job
classad, reading the documentation on SYSTEM_JOB_MACHINE_ATTRS it seems
like the value is set when the schedd initiates the start up of the job
but our script will be running after the job starts. Is there any way
to have the job classad update during or at the end of the job's run?
Thanks for the help,
On Fri, 2022-03-04 at 14:48 -0600, Todd L Miller wrote:
> The technique at
> is limited, as you have discovered, to machine ad attributes set when
> job matches the machine, so that won't work for what you want.
> There are two other ways you can edit the (schedd's copy of
> ClassAd of a job running at a startd.
> (1) You can run condor_chirp from inside the job.
> (2) You can set job_machine_attrs in the job submit file.
> (3) You can set SYSTEM_JOB_MACHINE_ATTRS on the submit node.
> The disadvantage of (2) and (3) is that the attribute that
> into the job ClassAd is named `MachineAttr<Name>0`, and not just
> - ToddM
> 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: