Bacula-users

Re: [Bacula-users] How to prevent to schedule a job if the same job is still running

2009-09-15 10:47:47
Subject: Re: [Bacula-users] How to prevent to schedule a job if the same job is still running
From: Silver Salonen <silver AT ultrasoft DOT ee>
To: Stephen Thompson <stephen AT seismo.berkeley DOT edu>
Date: Tue, 15 Sep 2009 17:43:56 +0300
On Tuesday 15 September 2009 17:36:25 Stephen Thompson wrote:
> Silver Salonen wrote:
> > Actually, you can do it - "Allow Higher Duplicates" really means ANY
> > duplicate job, not only a higher one. I just tested it and an incremental
> > job is cancelled if either full or incremental instance of the same job
> > is still running.
> >
> > So in my case "Allow Higher Duplicates" did the trick :)
> 
> Really?
> 
> This is exactly what I want and what I tried for when 3.x was first
> released, but my experiments showed that nothing was canceled.  The jobs
> rather began running concurrently.
> 
> I'll try this again.  Are you saying to set Allow Higher Duplicates to
> Yes or No?  Actually, could you possibly list what you have all the
> relevant values set to?  I would most appreciate it.
> 
> thanks,
> Stephen

Yeah, I was positively surprised today too :)

I have just one option in every JobDefs for that:
Allow Higher Duplicates = no

-- 
Silver

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users