On Wed, 22 Mar 2006 22:55:17 +0100
Kern Sibbald <[EMAIL PROTECTED]> wrote:
> On Wednesday 22 March 2006 22:19, Carles Bou wrote:
> > Some one has send me a mail telling that bacula only supports datetime
> > encoding in US format i've changed this parameter in the postgresql.conf
> > and bacula is
On Wednesday 22 March 2006 22:19, Carles Bou wrote:
> Some one has send me a mail telling that bacula only supports datetime
> encoding in US format i've changed this parameter in the postgresql.conf
> and bacula is running right!!
>
> Will this be solved in futures versions?
I hope there is some
Hello,
On 3/22/2006 10:19 PM, Carles Bou wrote:
Some one has send me a mail telling that bacula only supports datetime
encoding in US format
i've changed this parameter in the postgresql.conf and bacula is running
right!!
Will this be solved in futures versions? Because i don't want to have 1
Some one has send me a mail telling that bacula only supports datetime encoding
in US format
i've changed this parameter in the postgresql.conf and bacula is running right!!
Will this be solved in futures versions? Because i don't want to have 1
postgresql server
running only for bacula, and an
yes, her's part of my bacula-dir conf and bacula-fd.
I'm not posting the SD conf because files are writed on the tapechanger
=bacula-dir==
JobDefs {
Name = "DefaultJob"
Type = Backup
Level = Incremental
Client = kaneda-fd
Schedule = "WeeklyCyc
Hello Alan,
no i've no scripts running, here is the stat of a file in the set
File: `File_Name.xls'
Size: 28269 Blocks: 56 IO Block: 131072 regular file
Device: 811h/2065d Inode: 1500Links: 1
Access: (0777/-rwxrwxrwx) Uid: (0/root) Gid: (0/roo