On 2007.10.30. 17:51, Chris Hoogendyk wrote: > > Ryan Novosielski wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Are you certain that the DST dates did not move in your area? I'm not >> sure which zones expanded DST and which did not. I realize that is not >> your question, but it is something I wanted to mention, since my >> timezone does not switch until Nov 4th. >> >> That said, I'd expect Bacula will skip the backup, given its behavior in >> this case. One way to solve this problem, I guess, would be to never >> start backups between 2 and 3 AM. > > yup. > > Daylight Savings time laws changed affective spring 2007 in the U.S. and > Australia. I have no clue about the Czech Republic or others. There were > patches to be applied according to your operating system. I applied > Solaris 9 patches. Mac OS X and Windows systems got theirs by automatic > updates. One of our labs had an older Sun OS 5.6 system for which there > were no patches. After messing with it for a while, they finally punted > and said it didn't really matter. ...
i don't think timezone changes was the question here :) actual question would be - how does bacula actually handle these times. i also had one job executed twice, but given that it's still 1.36, i didn't bother much. so, is there some dst intelligence in latest versions of bacula ? if not, maybe a comment, warning about this should be added to default configuration file schedules :) -- Rich ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users