Re: [HTCondor-users] Job status of jobs when using USER_JOB_WRAPPER

[Brian Bockelman <bbockelm@xxxxxxxxxxx>]

Hi Weiming,

The job's exit status will be the Unix exit status of the process launched by HTCondor.  If a USER_JOB_WRAPPER is used, then it is the exit status of the wrapper.

NOTE - HTCondor launches the USER_JOB_WRAPPER, with the expectation that the job wrapper will call 'exec' on the user's binaries.  So,
- If the job wrapper succeeds in calling 'exec', then the job's exit status refers to the command requested by the user.
- If the job wrapper fails in calling 'exec', then the job's exit status refers to the exit status of the wrapper.

Since the setup can be awfully confusing for end-users, it's suggested that job wrappers are used sparingly - or, at least, kept relatively simple!

Brian

> On Apr 1, 2017, at 4:40 AM, Weiming Shi <swmtrc@xxxxxxxxx> wrote:
> 
> Dear Condor users and developers,
> 
> I have  a question regarding to the job status returned by 'condor_q
> -nobatch' when USER_JOB_WRAPPER is used. I am trying to understand if
> the returned Job Status of the status of the user job wrapper or the
> status of the user application wrapped by the user job wrapper?
> 
> Thanks
> 
> 
> Weiming
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
> 
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/