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

Re: [Condor-users] Having condor_startd perform actions as root before each job start?

The examples given in the manual article you reference talk
about either using a hook to fetch work, or to route jobs.
The activity I'm doing really isn't either of those.. are there
other descriptions of the hook mechanism elsewhere? It looks
like the hook mechanism is generic enough but the documentation isn't.

Steve Timm

On Mon, 24 Oct 2011, Tim St Clair wrote:

My 1st reaction to this would be job hooks:


Is there a reason this would not work?


----- Original Message -----
From: "Steven Timm" <timm@xxxxxxxx>
To: condor-users@xxxxxxxxxxx
Sent: Monday, October 24, 2011 1:32:36 PM
Subject: [Condor-users] Having condor_startd perform actions as root before	each job start?

I recently deployed a configuration with SLOTx_EXECUTE
with a separate file system defined for each of 20 slots on an execution

In the current configuration, condor makes a subdirectory in
the SLOTx_EXECUTE directory and cleans it up on exit, or when
condor restarts.  My question--instead of just doing an
rm -Rf, can I actually have the condor_startd execute
a script, as root,  which removes the old file system and
re-instantiates a whole new file system?


Steven C. Timm, Ph.D  (630) 840-8525
timm@xxxxxxxx  http://home.fnal.gov/~timm/
Fermilab Computing Division, Scientific Computing Facilities,
Grid Facilities Department, FermiGrid Services Group, Group Leader.
Lead of FermiCloud project.