On Mar 3, 2008, at 2:50 AM, [EMAIL PROTECTED] wrote: > Message: 16 > Date: Mon, 03 Mar 2008 11:00:41 +0100 > From: Arno Lehmann <[EMAIL PROTECTED]> > Subject: Re: [Bacula-users] Double/over scheduling > To: bacula-users@lists.sourceforge.net > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi, > > 03.03.2008 07:59, Jesse Peterson wrote: >> Hello, >> >> Firstly I want to thank the developers, contributors and users for >> helping make bacula a great product! For whatever it's worth it is >> of great use to us with Mac OS X, NetBSD, Linux and Windows! >> >> Secondly I'd like to ask is it known and acceptable that when a Job >> is already scheduled and its schedule passes another duplicate job >> gets scheduled? > > This is know and this is how Bacula's scheduler works. In my opinion, > this is a design issue and not a bug.
I would agree. > > ... >> THis seems like it should be avoidable. I imagine an option that >> makes jobs not get scheduled if the same job (job >> name,schedule,pool,etc.) already exists in the queue (only >> difference being the scheduled time). THoughts? > > No need for furher thoughts :-) > > This is currently being worked on - having a final result might take a > while, though - and your idea was one of the options discussed. Well for whatever it's worth here's to the solution. > > Search for the mails with a subject of "Redundant Run in Schedule" in > the list archives, both -users and -devel, and you'll even find a > patch :-) Good to know that this is on the collective books as it were. I'll look into the archives. Thank you! - Jesse ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
