[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] Hooks in HTCondor-CE?
- Date: Wed, 18 Mar 2020 13:04:34 -0500
- From: Brian Lin <blin@xxxxxxxxxxx>
- Subject: Re: [HTCondor-users] Hooks in HTCondor-CE?
So your current setup is running your scripts on the CE? If that's the
case, I suggest taking a look at the cleanup hook:
On 3/18/20 9:45 AM, jcaballero.hep@xxxxxxxxx wrote:
our case would be how to keep custom made functionalities if we
migrate our site from ARC-CE to HTCondor-CE.
We have a bunch of scripts that run at job completion. Like copying
job files to storage, and stuff like that.
So I am looking for the easiest way to maintain those functionalities,
to be performed at job completion.
I thought about the hooks, since I did some work with them in the past.
Just wondering if the hooks is the best/easiest way, or there are better ways.
El miÃ., 18 mar. 2020 a las 14:36, Brian Lin (<blin@xxxxxxxxxxx>) escribiÃ:
I'm curious what your use case is here -- is this related to ATLAS'
interest in pre-staging container images specified by incoming grid
jobs? What actions are you looking to perform at which specific points
in the job's lifetime? Is this for a CE in front of HTCondor or another
As Michael pointed out, HTCondor has a multitude of hooks but some of
them are specific to startds and so those wouldn't be applicable to
On 3/17/20 4:15 AM, Jose Caballero wrote:
And, would these hooks have access to the jobâs output files?
Let me clarify the question. Is the path to job files (stdout, stderr,
output files) one the classads at the CE?
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
You can also unsubscribe by visiting
The archives can be found at: