Hi,
27.02.2008 09:29, Carsten Menke wrote:
> Dan Langille wrote:
>>
>>
>> Solution so that the 4th Friday job is not run if there is a 5th Friday:
>>
>> shell script which runs as RunBeforeJob. Verify that today + 7 days is
>> still this month.
>> If it is, error out and the job will not run.
>>
Dan Langille wrote:
>
>
>
> Solution so that the 4th Friday job is not run if there is a 5th Friday:
>
> shell script which runs as RunBeforeJob. Verify that today + 7 days is
> still this month.
> If it is, error out and the job will not run.
>
Thanx for that :-) But what I meant is, should
On Feb 26, 2008, at 9:41 PM, Carsten Menke wrote:
> Hi,
>
> due to the recent discussion about improving scheduling, I think
> what is
> more important is, that you have the ability to run a job on the
> last Friday of
> the month, for example. To provide a real monthly cycle. Currently
> y
Hi,
due to the recent discussion about improving scheduling, I think what is
more important is, that you have the ability to run a job on the last Friday of
the month, for example. To provide a real monthly cycle. Currently you could
specify this only as "4th-5th Fri" (to the best of my knowledg
On Tuesday 26 February 2008 17.45:23 David Boyes wrote:
> > > => Job Proximity = (0)
> > > => Finally Job Proximity is to allow a bit of overlap. For example,
>
> if
>
> > a
> >
> > > job has => been running 20 minutes or ran 20 minutes ago, you might
>
> want
>
> > to
> >
> > > not apply => t
> > => Job Proximity = (0)
> > => Finally Job Proximity is to allow a bit of overlap. For example,
if
> a
> > job has => been running 20 minutes or ran 20 minutes ago, you might
want
> to
> > not apply => the rules.
> >
> > Could you elaborate on what this means to you a bit more?
>
> I think
