Re: [HTCondor-users] trigger STARTD_CRON_NODEHEALTH_EXECUTABLE at condor start

[Michael Pelletier <Michael.V.Pelletier@xxxxxxxxxxxx>]

The main difference is that the RunBenchmarks attribute governs when benchmarks are run, while a OneShot startd_cron is run at startup, and reconfig if configured to do so.

Michael V. Pelletier
Information Technology
Digital Transformation & Innovation
Integrated Defense Systems
Raytheon Company

-----Original Message-----
From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> On Behalf Of John M Knoeller
Sent: Friday, August 2, 2019 10:12 AM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: [External] Re: [HTCondor-users] trigger STARTD_CRON_NODEHEALTH_EXECUTABLE at condor start

yes, the BENCHMARKS are a lot like the STARTD_CRON jobs, they both handle output the same. 

-----Original Message-----
From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> On Behalf Of Beyer, Christoph
Sent: Friday, August 2, 2019 1:25 AM
To: htcondor-users <htcondor-users@xxxxxxxxxxx>
Subject: Re: [HTCondor-users] trigger STARTD_CRON_NODEHEALTH_EXECUTABLE at condor start

Hi Michael,

interesting and yes, never thought about that as I do not do any benchmarking at the moment. 

Does the benchmarking executable export automatically it's output in the startd environment as the startd-cron does ? 

Best
Christoph

-- 
Christoph Beyer
DESY Hamburg
IT-Department