Re: [HTCondor-users] ep custom configuration

[Steffen Grunewald <steffen.grunewald@xxxxxxxxxx>]

On Fri, 2025-04-25 at 15:24:34 +0200, Antonio Falabella wrote:
> Dear Steffen,
> 
> Is there docs for the STARD_CRON? could you point me to that?

htcondor.readthedocs.io

or borrow code somewhere, like I borrowed this years ago (I'm rewriting
it not to disclose the original - please bear with my typos):

- in the condor_config, add a STARTD_CRON job:
# MYCRON setup
MYCRON                         = /etc/condor/modules/mycron
STARTD_CRON_JOBLIST            = $(STARTD_CRON_JOBLIST) MYCRON
STARTD_CRON_MYCRON_EXECUTABLE  = $(MYCRON)
STARTD_CRON_MYCRON_PERIOD      = 600

(you'd want this to run more often...)

- in /etc/condor/modules/mycron:
# Get the info to characterize machine state
PROCESSCOUNT=`ps auxw | grep [d]atatask | wc -l`
# Convert into something that looks like a ClassAd attribute
if [ ${PROCESSCOUNT} != 0 ]
then
  DATATASK=True
else
  DATATASK=False
# Write to stdout
echo DATATASK_RUNNING=${DATATASK}


As the name says, this would add a single attribute to the Machine ClassAds,
as all that is written to stdout in such a STARTD_CRON executable will end up
in the ClassAd.
You'd "only" need something that detects the machine being "in special use".
I guess you'll have to restart the STARTD and wait a while for the attribute
to show up in the "condor_status -l ${node}" output.

> What's  your thoughts about the condor_kbdd-like thing?

Never used that (there are no keyboards connected to our pool machines), so I
don't know how to fake X events or USB keyboard activity - and the condor_kbdd
docs don't look too promising in this respect. YMMV though.

Best,
 Steffen


--
Steffen Grunewald, Cluster Administrator
Max Planck Institute for Gravitational Physics (Albert Einstein Institute)
Am Mühlenberg 1 * D-14476 Potsdam-Golm * Germany
~~~
Fon: +49-331-567 7274
Mail: steffen.grunewald(at)aei.mpg.de
~~~