On 18 Aug 2007 at 2:00, Per olof Ljungmark wrote:
> Since upgrading to 2.2.0 bsmtp sets the wrong Date: header in the mail:
> Date: Sat, 18 Aug 2007 01:48:56 + (CEST)
>
> For the recipient the above message appears to have been receieved at
> 03:48, two hours ahead.
>
> The correct timezone
Since upgrading to 2.2.0 bsmtp sets the wrong Date: header in the mail:
Date: Sat, 18 Aug 2007 01:48:56 + (CEST)
For the recipient the above message appears to have been receieved at
03:48, two hours ahead.
The correct timezone is UTC +2, the above header should have read
Date: Sat, 18 Aug 2
Hi Martin,
On Friday 17 August 2007 04:46:24 pm you wrote:
> > where x.x.x.227 is client's external NIC address, x.x.x.136 is bacula
> > server's external address; 192.168.0.{253,200} are the corresponding
> > private addresses. As you can see, while fd daemon on client has indeed
> > been bound t
Martin Simmons wrote:
>> On Fri, 17 Aug 2007 19:27:17 +0200, Per olof Ljungmark said:
>> Per olof Ljungmark wrote:
>>> So,
>>>
>>> What did I do wrong here?
>>>
>>> I upgraded bacula from 2.0.3 to 2.2.0, FreeBSD 6.
>>> Yesterdays nightly job failed big time, each backup failed with
>>>
>>> 16-A
> On Thu, 16 Aug 2007 16:36:48 -0400, Ivan Adzhubey said:
>
> Hi,
>
> I am having trouble with my dual-NIC servers: it seems there is no way to
> force bacula client on a remote server use a particular fixed
> interface/address for data transfers. Even though I have set FDAddress to a
> pr
> On Thu, 16 Aug 2007 14:38:40 -0500 (CDT), Andrew Noonan said:
> Importance: Normal
>
> On Thu, August 16, 2007 2:29 pm, Martin Simmons <[EMAIL PROTECTED]> said:
>
> >> On Thu, 16 Aug 2007 12:02:05 -0500 (CDT), Andrew Noonan said:
> >> Importance: Normal
> >>
> >> Hi all,
> >>
> >>
> On Fri, 17 Aug 2007 12:21:02 +0200, Juan Asensio Sánchez said:
>
> Hi
>
> I am tetsing Bacula. I have configured it to work with mysql. I have
> one pool with only one tape. There are 5 jobs to be backed up on that
> tape. Jobs are running weekly. This is the pool configuration:
>
> Pool {
> On Fri, 17 Aug 2007 19:27:17 +0200, Per olof Ljungmark said:
>
> Per olof Ljungmark wrote:
> > So,
> >
> > What did I do wrong here?
> >
> > I upgraded bacula from 2.0.3 to 2.2.0, FreeBSD 6.
> > Yesterdays nightly job failed big time, each backup failed with
> >
> > 16-Aug 21:46 candyman-
> On Fri, 17 Aug 2007 13:51:34 -0400, Dan Langille said:
>
> Has anyone encountered this situation? The pwd of the
> RunBeforeScript is the directory into which the source code was
> unpacked.
>
> To reproduce, use this RunBeforeScript:
>
> #!/bin/sin
> echo $PWD
>
> The output is:
>
>
On 8/17/07, Alan Brown <[EMAIL PROTECTED]> wrote:
> On Fri, 17 Aug 2007, Drew Bentley wrote:
>
> > Yeah, autoextend for InnoDB seems to have bitten you. I usually never
> > do this and have monitors to tell me if it's reaching a certain
> > threshold, as you're probably not even using all of the In
Has anyone encountered this situation? The pwd of the
RunBeforeScript is the directory into which the source code was
unpacked.
To reproduce, use this RunBeforeScript:
#!/bin/sin
echo $PWD
The output is:
17-Aug 13:28 ducky-dir: BeforeJob: run command
"/home/dan/bin/test_pwd"
17-Aug 13:28 du
On Fri, 17 Aug 2007, Drew Bentley wrote:
> Yeah, autoextend for InnoDB seems to have bitten you. I usually never
> do this and have monitors to tell me if it's reaching a certain
> threshold, as you're probably not even using all of the InnoDB space
> allocated, as it's not particularly nice in gi
Per olof Ljungmark wrote:
> So,
>
> What did I do wrong here?
>
> I upgraded bacula from 2.0.3 to 2.2.0, FreeBSD 6.
> Yesterdays nightly job failed big time, each backup failed with
>
> 16-Aug 21:46 candyman-sd: Volume "UNW259L2" previously written, moving
> to end of data.
> 16-Aug 21:47 candy
On 8/17/07, Alan Brown <[EMAIL PROTECTED]> wrote:
> On Fri, 17 Aug 2007, Alan Brown wrote:
>
> > innodb_data_file_path = ibdata1:26000M;ibdata2:2000M:autoextend
> >
> > (As I understand it, this should grow the tablespace as needed)
>
> Doh!
>
> FilesystemSize Used Avail Use% Mounted o
On Thu, 16 Aug 2007, Drew Bentley wrote:
> You'll either need to add more InnoDB by adding more to your
> /etc/my.cnf file or convert the tables to use MyISAM. Usually depends
> on what MySQL will use as default or if someone else created the
> InnoDB space but you can easily add more by editing t
On Fri, 17 Aug 2007, Alan Brown wrote:
> innodb_data_file_path = ibdata1:26000M;ibdata2:2000M:autoextend
>
> (As I understand it, this should grow the tablespace as needed)
Doh!
FilesystemSize Used Avail Use% Mounted on
/dev/mapper/VolGroupMSSLAY01-LogVolSQL
I'm trying to create internal documentation for others to install the
bacula-fd on various windows computers around here. I just installed
bacula 2.2.0. Since it didn't give me most of the configuration screen
prompts, I decided to backup my config file then uninstall it. The
uninstaller se
On Thu, 16 Aug 2007, Ivan Adzhubey wrote:
> I have a Linux NFS fileserver which has to be backed up to a bacula server on
> another Linux box. The fileserver in question exports everything that's
> needed to be backed up so all files are actually accessible on bacula server
> via NFS as well. Shou
Hi
I am tetsing Bacula. I have configured it to work with mysql. I have
one pool with only one tape. There are 5 jobs to be backed up on that
tape. Jobs are running weekly. This is the pool configuration:
Pool {
Name = PoolCintasDiariasMartes
Pool Type = Backup
AutoPrune
So,
What did I do wrong here?
I upgraded bacula from 2.0.3 to 2.2.0, FreeBSD 6.
Yesterdays nightly job failed big time, each backup failed with
16-Aug 21:46 candyman-sd: Volume "UNW259L2" previously written, moving
to end of data.
16-Aug 21:47 candyman-sd: mars.2007-08-16_21.30.02 Error: Bacula
* Steen <[EMAIL PROTECTED]> [16.08.2007]:
> On Thursday 16 August 2007 21:30:36 Stephan Mueller wrote:
> > Hi,
> >
> > if I remember correctly, in older versions bacula preferred unused
> > volumes over purged ones, so that all volumes were used over the time.
> >
> > I now have switched to an usb
21 matches
Mail list logo
