On Sun, Oct 30, 2005 at 06:55:36PM -0500, Phil Stracchino wrote:
> Ross Boylan wrote:
> > I can explain the duplicate jobs, but not the primary problem of the
> > commented out job being run.
>
> Suggestion: Rather than commenting out a job to disable it without
> restarting, change its Schedule to a null schedule:
>
> Schedule {
> Name = NEVER
> }
>
> Job {
> Name = foo
> Schedule = NEVER
> ...
> }
>
>
> THEN, after reloading, you can comment it out if you want. Either that,
> or comment it out and *restart*, not reload, Bacula. If you just
> comment it out and reload, the existing job definition remains in memory
> as scheduled, because you aren't overwriting the definition with
> anything different.
Would it be reasonable to file a bug about this? It seems like either
a bug or an undesirable feature.
>
>
> > Last night the clocks jumped back because of daylight savings time.
> > My jobs are scheduled for 1:05am, and that happened twice. This is a
> > known problem, though the solution is unclear. See bacula bug 153.
>
> This is why I stopped scheduling jobs between 0100 and 0200. I just
> moved them from 0115 to 0215.
I think clocks jump forward from 2 to 3. Would that mean jobs
scheduled for 2:15am get skipped that day?
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
