Yup, I tried a number of values including 1 and a few >100
On Fri, Aug 3, 2012 at 2:17 AM, Reuti <[email protected]> wrote: > Am 03.08.2012 um 06:51 schrieb David Erickson: > >> On Thu, Aug 2, 2012 at 4:59 PM, Reuti <[email protected]> wrote: >>> Am 03.08.2012 um 01:54 schrieb David Erickson: >>> >>>> Also according to the manual queue_conf: >>>> >>>> Exit codes for the epilog attribute can be interpreted based on the >>>> following exit values: >>>> 0: Success >>>> 99: Reschedule job >>>> 100: Put job in error state >>>> Anything else: Put queue in error state >>>> >>>> I've had no luck with the "Anything else" exit codes, they never seem >>>> to put the queue into an error state. To pause things (and enable the >>>> existing job to be re-run), I've decided to exit with code 100 when >>>> the job has a non zero exit code, and suspend the queue using qmod -s >>>> <queue>. >>> >>> Which version are you running? >> >> 6.2u4-2ubuntu1 > > I didn't see such a behavior in the past with this version. I'm not sure what > Ubuntu patched there though. > > The exit code of the epilog script is set by "exit 15" or alike? > > -- Reuti _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
