Martin Simmons wrote:
>> On Tue, 07 Apr 2009 16:45:54 +0200, Foo said:
>>
>> On Mon, 06 Apr 2009 19:41:52 +0200, Martin Simmons
>> wrote:
>>
>>
On Mon, 06 Apr 2009 17:34:09 +0200, Foo said:
The best solution would be for Bacula
On Tue, 07 Apr 2009 20:23:49 +0200, Martin Simmons
wrote:
>> On Tue, 07 Apr 2009 16:45:54 +0200, Foo said:
>>
>> Basically on startup Bacula needs to check the locale, get the offset
>> from
>> UTC, if any, and set its internal clock to UTC, and change the offset on
>> DST changes. Then
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Foo wrote:
> On Mon, 06 Apr 2009 19:41:52 +0200, Martin Simmons
> wrote:
>
>>> On Mon, 06 Apr 2009 17:34:09 +0200, Foo said:
>>> The best solution would be for Bacula to translate time to UTC
>>> internally
>>> for scheduling, everything ext
On Wed, Apr 8, 2009 at 5:23 AM, Martin Simmons wrote:
>> On Tue, 07 Apr 2009 16:45:54 +0200, Foo said:
>>
>> On Mon, 06 Apr 2009 19:41:52 +0200, Martin Simmons
>> wrote:
>>
>> >> On Mon, 06 Apr 2009 17:34:09 +0200, Foo said:
>> >>
>> >> The best solution would be for Bacula to translate
Foo wrote:
> On Mon, 06 Apr 2009 19:41:52 +0200, Martin Simmons
> wrote:
>
>
>>> On Mon, 06 Apr 2009 17:34:09 +0200, Foo said:
>>>
>>> The best solution would be for Bacula to translate time to UTC
>>> internally
>>> for scheduling, everything external such as logfil
> On Tue, 07 Apr 2009 16:45:54 +0200, Foo said:
>
> On Mon, 06 Apr 2009 19:41:52 +0200, Martin Simmons
> wrote:
>
> >> On Mon, 06 Apr 2009 17:34:09 +0200, Foo said:
> >>
> >> The best solution would be for Bacula to translate time to UTC
> >> internally
> >> for scheduling, everyth
On Mon, 06 Apr 2009 23:38:38 +0200, John Lockard
wrote:
> The time jumps at 2am, either forward or backward depending on
> whether you're switching to or from DST. Most admins I know
> just completely avoid the time period from 1:00am to 3:00am.
> entirely because of the Daylight Saving Time s
On Mon, 06 Apr 2009 19:41:52 +0200, Martin Simmons
wrote:
>> On Mon, 06 Apr 2009 17:34:09 +0200, Foo said:
>>
>> The best solution would be for Bacula to translate time to UTC
>> internally
>> for scheduling, everything external such as logfiles, scheduling stanzas
>> in config etc. woul
The time jumps at 2am, either forward or backward depending on
whether you're switching to or from DST. Most admins I know
just completely avoid the time period from 1:00am to 3:00am.
entirely because of the Daylight Saving Time switches.
If you're going to go UTC, then you should go UTC all the
> On Mon, 06 Apr 2009 17:34:09 +0200, Foo said:
>
> The best solution would be for Bacula to translate time to UTC internally
> for scheduling, everything external such as logfiles, scheduling stanzas
> in config etc. would remain in the user's locale.
That doesn't help, because saying 2
On Sun, 05 Apr 2009 09:29:48 +0200, Kevin Keane
wrote:
> Mark V wrote:
>> Two questions:
>> Q1) Am I going mad or is it possible for bat to show an error that
>> does not show in the bacula log file?
>>
> I don't know
I've seen Bat hijack output away from an open bconsole, though I'm not
sur
Mark V wrote:
> Hi Group,
>
> Unfortunately I seem to have scheduled my full backup for 2:05am which
> is around the time that our clocks go back, 2:00am - I use openSUSE
> 11.0 and it seems this time shift happened, but only after the backup
> started.
>
> bacula version is 2.4.4
>
> The result do
Mark V wrote:
> Hi Group,
>
> Unfortunately I seem to have scheduled my full backup for 2:05am which
> is around the time that our clocks go back, 2:00am - I use openSUSE
> 11.0 and it seems this time shift happened, but only after the backup
> started.
>
> bacula version is 2.4.4
>
> The result do
Mark V wrote:
> Hi Group,
>
> Unfortunately I seem to have scheduled my full backup for 2:05am which
> is around the time that our clocks go back, 2:00am - I use openSUSE
> 11.0 and it seems this time shift happened, but only after the backup
> started.
>
> bacula version is 2.4.4
>
> The result do
Mark V wrote:
> Hi Group,
>
> Unfortunately I seem to have scheduled my full backup for 2:05am which
> is around the time that our clocks go back, 2:00am - I use openSUSE
> 11.0 and it seems this time shift happened, but only after the backup
> started.
>
> bacula version is 2.4.4
>
> The result do
AFAIK answer for Q3 is to set this job to far away. this mean 1h forward to
3:05 am.
Greets
Pawel Madej
On niedziela, 5 kwietnia 2009 08:37:25 Mark V wrote:
> Hi Group,
>
> Unfortunately I seem to have scheduled my full backup for 2:05am which
> is around the time that our clocks go back, 2:00
Hi Group,
Unfortunately I seem to have scheduled my full backup for 2:05am which
is around the time that our clocks go back, 2:00am - I use openSUSE
11.0 and it seems this time shift happened, but only after the backup
started.
bacula version is 2.4.4
The result does not seem to be disastrous -
17 matches
Mail list logo
