Re: [help-gnubatch] repeating jobs

[andrew warshaver]

Todd,

I likewise thought that is what the option does.  The next run time is
advanced (or not) depending the option correctly.  But the job status
is not affected by this option, and the next run will not kick off if
the job is in an Err state.  I don't think you have any recourse here
except to NOT err out , or else, you could set a variable on err , and
then do something (e.g. gbch-jchange -N).  But I would have to
reccomend the former.

Cheers,
Andrew

On Fri, Sep 24, 2010 at 1:58 PM, Todd Jackson <address@hidden> wrote:
>    Hi.  I have some jobs set up in gnubatch that repeat every hour,
> but I'm occasionally having a problem where the job goes into 'Err'
> status in gbch-q and stays that way.  I can restart it with the r
> command from the queue display, but it seems like the job should
> restart by itself at the next repeat interval.
>    From the reference manual, this seems to be controlled by the
> advance-time-error flag, and for the jobs that get stuck in the error
> state this flag is set to 'advance-time-error', not
> 'no-advance-time-error'.
>    Is there something else I should be doing to get these jobs to
> restart at the next hourly repeat interval?  Thanks!
>    I'm using gnubatch v 1.2, on a CentOS 5.5 system.
>
>     -- Todd
>
>