Well, I've got "Maximum Concurrent Jobs = 3", so it looks like the duplicate 
job control does quite the same as "Maximum Concurrent Jobs = 1", which is 
weird enough :)

PS. I haven't tried or tested this more, so maybe we're missing smth.

-- 
Silver

On Monday 04 May 2009 20:44:22 Stephen Thompson wrote:
> 
> That's the behaviour I've seen when I set   Maximum Concurrent Jobs = 1
> under JobDefs.  Then only one job with the same name can run at a time.
> What I was hoping for with duplicate job control was for the subsequent 
> job(s) to be canceled so that they wouldn't run at all.
> 
> thanks,
> Stephen
> 
> 
> 
> Silver Salonen wrote:
> > Hello.
> > 
> > I noticed one thing today.. a big full backup was ran on friday, so it 
wasn't 
> > completed 24 hours later, but when the next job's time arrived, it wasn't 
run. 
> > I was very surprised, because I expected it to run as it has been the case 
> > without "allow duplicate jobs = no" with Bacula 2.x. When the full job 
> > completed, the scheduled (and not run) one started immediately and was 
> > correctly making an incremental backup.
> > 
> > So it seems that duplicate job control does work, just not the way I 
expected, 
> > ie. I expected it to being cancelled (I guess I thought it's the "Cancel 
> > Queued Duplicates" directive, but now, I guess not) instead of being 
hidden 
> > and waiting somewhere back there.

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users