Re: [Condor-users] Running a HOOK_JOB_EXIT

[Colin Leavett-Brown <crlb@xxxxxxx>]

Hi Ian, I tried the "STARTD" version just prior to your first post 
arriving. So now I've tried the test again using your config statements 
verbatim:

2. Hook config:
# Job hooks
STARTER_JOB_HOOK_KEYWORD = MYHOOK
MYHOOK_HOOK_JOB_EXIT = /usr/local/bin/munin-node-condor-job-exit

But it still does not work. By the way, the 7.6 manual, section 4.4.1.2 
says "... the /condor_startd/ will use a global keyword as defined by 
STARTD_JOB_HOOK_KEYWORD". But none of the three configs have worked and 
I'm not sure what to try next.

Thanks again for your help, Colin.

Ian Chesal wrote:
> On Thursday, June 16, 2011 at 5:01 PM, Colin Leavett-Brown wrote:
>
> > I just tried modifying the condor config so that the output from step 2
> > now reads:
> >
> > 2. Hook config:
> > # Job hooks
> > STARTD_JOB_HOOK_KEYWORD = ALL
> > ALL_HOOK_JOB_EXIT = /usr/local/bin/munin-node-condor-job-exit
> >
> > But it still does not work.
> That should be STARTER_JOB_HOOK_KEYWORD, not STARTD_JOB_HOOK_KEYWORD. 
> The exit hook is a condor_starter hook, not a condor_startd hook.
>
> Regards,
> - Ian
>
> ---
> Ian Chesal
>
> Cycle Computing, LLC
> Leader in Open Compute Solutions for Clouds, Servers, and Desktops
> Enterprise Condor Support and Management Tools
>
> http://www.cyclecomputing.com
> http://www.cyclecloud.com
> http://twitter.com/cyclecomputing

--
Colin Leavett-Brown
Department of Physics & Astronomy
University of Victoria
250-721-7728