On Saturday 04 October 2008 07:43:14 James Harper wrote:
> Just a couple more dependencies I was missing that weren't explicitly
> noted in the README file:
>
> python
> unzip
>
> I am building this in a xen virtual machine that I debootstrap'd
> especially for bacula testing, which is why it was m
On Saturday 04 October 2008 18:37:54 John Drescher wrote:
> Would it be too difficult to make this file work like .cvsignore
> instead of just ignoring the current folder and its children? I can
> see this being a lot more flexible but more difficult in
> implementation and usage.
>
> http://glast-
Just a couple more dependencies I was missing that weren't explicitly
noted in the README file:
python
unzip
I am building this in a xen virtual machine that I debootstrap'd
especially for bacula testing, which is why it was missing python - I'd
only installed that which I had had some need to in
The attached updated patch allows the build-win32-cross-tools script to
execute successfully. gcc appears to incorrectly detect texinfo too, but
that doesn't stop it building so I haven't attempted to fix it.
James
bacula_mingw32_binutils_fix.patch
Description: bacula_mingw32_binutils_fix.patch
The attached patch gets binutils past the point it was failing at
previously when the installed texinfo version was > 4.9
Now I'm getting this error:
cc1: warnings being treated as errors
/usr/local/src/bacula/cross-tools/source/binutils-2.16.91-20060119-1/gas
/app.c: In function 'do_scrub_chars'
I'm attempting a win32 cross compile under Linux so I can do some plugin
testing, but I'm getting an error.
It looks like binutils-2.16.91-20060119-1-src.tar.gz has to have a valid
version of texinfo, even though at first glance it would cope with it
being missing.
Unfortunately, a 'valid version
On Wed, 2008-10-01 at 09:07 +0200, Kern Sibbald wrote:
> On Wednesday 01 October 2008 08:32:53 Yuri Timofeev wrote:
> > Hi
> >
> > I installed CentOS 5.2 for my production Bacula server.
> > I could build rpm from rpms packages for centos5 and send them to be
> > posted on sourceforge.
> > Is it re
On Fri, 2008-10-03 at 20:22 +0200, Kern Sibbald wrote:
> Hello,
>
> It is not too late to change the name of the directive, but I would like to
> see some discussion/input on this. Although I don't have any strong
> attachment to "Ignore Dir", I think I personally prefer it to "Exclude Flag
On Oct 3, 2008, at 1:19 PM, Marc Schiffbauer wrote:
> I did not mean the value of the directive but the name of the
> directive itself.
>
> Everywhere in the FileSet in Bacula you use the word "Exclude" when
> dealing with files that will not be backed up. So I suggest to
> follow this terminolog
On Wed, 2008-10-01 at 09:07 +0200, Kern Sibbald wrote:
> On Wednesday 01 October 2008 08:32:53 Yuri Timofeev wrote:
> > Hi
> >
> > I installed CentOS 5.2 for my production Bacula server.
> > I could build rpm from rpms packages for centos5 and send them to be
> > posted on sourceforge.
> > Is it re
Hello,
" I am not sure how the manual is generated, maybe adding version in
paranthesis after the option would be easy:
e.g. IgnoreDir (V3.0.0)
This way you only have to maintain one manual and if someone is reading a
manual and is using older version, he/she can easily m
On Oct 2, 2008, at 8:46 PM, Hemant Shah wrote:
>
> I am not sure how the manual is generated, maybe adding version in
> paranthesis after the option would be easy:
>
> e.g. IgnoreDir (V3.0.0)
>
> This way you only have to maintain one manua
In general, we maintain only the manual about to be
On Oct 2, 2008, at 5:52 PM, Dagan McGregor wrote:
>
>
>> -Original Message-
>> From: Hemant Shah [mailto:[EMAIL PROTECTED]
>> Sent: Friday, 3 October 2008 4:39 AM
>> To: bacula-users; Kern Sibbald
>> Cc: bacula-devel; [EMAIL PROTECTED]
>> Subject: Re: [Bacula-users] Bacula Status
>>
>> Ke
--- On Thu, 10/2/08, Kern Sibbald <[EMAIL PROTECTED]> wrote:
> From: Kern Sibbald <[EMAIL PROTECTED]>
> Subject: Re: [Bacula-devel] [Bacula-users] Bacula Status
> To: bacula-devel@lists.sourceforge.net, [EMAIL PROTECTED]
> Cc: "bacula-users" <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> Date: Thursda
On Oct 2, 2008, at 3:04 PM, Marc Schiffbauer wrote:
> * Kern Sibbald schrieb am 02.10.08 um 13:49 Uhr:
>> Hello,
>
> Hi Kern,
>
> this all sounds great!
>
>>
>> http://www.bacula.org/manuals/en/concepts/concepts/New_Features.html
>
> Ignore Dir
>
> A note on whether this directive works recursive
David Boyes wrote:
> Umm, not on the OSes I mentioned. If you fstat the file or read the
> directory inode with Unix compatibility on, the underlying OS reads the
> file once to determine the actual file size in bytes to fill into the
> file stat structure in order to be compatible with the assum
"David Boyes" <[EMAIL PROTECTED]> writes:
>> Bacula *must* read the entire file in order to back it up, so the
>> exact byte count is known with no extra cost.
>
> Umm, not on the OSes I mentioned. If you fstat the file or read the
> directory inode with Unix compatibility on, the underlying OS re
Kern Sibbald <[EMAIL PROTECTED]> writes:
> There is one important point that I would like to bring up, and that
> is that Bacula writes the attributes record (which contains the
> LStat) before it backs up the file (i.e. before it reads the file).
> This is because on the restore side, the File da
On Saturday 04 October 2008 18:29:54 Marc Schiffbauer wrote:
> * Kern Sibbald schrieb am 04.10.08 um 16:26 Uhr:
> > Hello Marc,
>
> Hello Kern,
>
> > I am sorry, but from what you wrote below, I really am not sure what you
> > like and what you do not like.
>
> I did not want to confuse you ;)
> I
On Oct 1, 2008, at 12:24 PM, Eli Shemer wrote:
>
>
> -Original Message-
> From: Dan Langille [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, October 01, 2008 4:58 PM
> To: Eli Shemer
> Cc: [EMAIL PROTECTED]; bacula-devel@lists.sourceforge.net
> Subject: Re: [Bacula-devel] rsync link behavior
On Oct 1, 2008, at 11:50 AM, Eli Shemer wrote:
> Hey there,
>
> After doing several incremental backups of our remote servers, I’ve
> noticed the backup sizes and transfer time are just too long.
> Making bacula almost completely improper for backing up remote
> servers with big single files.
Hello Bastian,
Could you retry your plugin test? There were a couple of problems with
calling the plugin close write subroutines that were almost surely the cause
or a cause of your problems.
Best regards,
Kern
On Tuesday 30 September 2008 09:52:15 Bastian Friedrich wrote:
> Hello Kern,
>
>
On Wednesday 01 October 2008 08:32:53 Yuri Timofeev wrote:
> Hi
>
> I installed CentOS 5.2 for my production Bacula server.
> I could build rpm from rpms packages for centos5 and send them to be
> posted on sourceforge.
> Is it really necessary?
I believe that we already have CentOS 5.2 rpms for B
Hello Bastian,
Since this is moderately complicated, to help me analyse this, could you
collect everything together into one email:
1. Your bacula-dir.conf file or the critical pieces
2. The Job listing of the backup output.
3. The exact command you used for the restore
4. The job listing of the
Marc Schiffbauer wrote:
> * Kern Sibbald schrieb am 04.10.08 um 16:26 Uhr:
>> Hello Marc,
>
> Hello Kern,
>
>> I am sorry, but from what you wrote below, I really am not sure what you
>> like
>> and what you do not like.
>
> I did not want to confuse you ;)
> I assumed that things like WildDir
Marc Schiffbauer wrote:
> * Kern Sibbald schrieb am 04.10.08 um 15:13 Uhr:
>> That seems to me to be a very good name.
>>
>> Concerning the placement of the directive: I think it is worth examining if
>> we
>> can easily move it to the Exclude { } section. In that case, the directive
>> name c
Hello Kern,
On Monday 29 September 2008, Kern Sibbald wrote:
> I just committed a minor but important change to fd_plugins.c that I hope
> will fix the problem you ran into.
Thx for this...
> Please try again, and if it dies, please send me another gdb traceback as
> you did previously.
... but
Hello,
I've just looked at the code and in at least one place, a loop over all the
instances of plugins is missing, and it is right where your seg fault occurs,
so that could well be the problem. I'll try to work on that tonight.
See below ...
On Monday 29 September 2008 16:55:55 Bastian Frie
On Mon, 2008-09-29 at 15:44 +0200, Kern Sibbald wrote:
> On Monday 29 September 2008 14:13:16 Brice Figureau wrote:
> > Hi,
> >
> > I was looking to the 2.4.2 SD spooling code lately (this was part of
> > understanding why despooling performances were not that good on my
> > hardware), when I notic
03.10.2008 20:22, Kern Sibbald wrote:
> Hello,
>
> It is not too late to change the name of the directive, but I would like to
> see some discussion/input on this. Although I don't have any strong
> attachment to "Ignore Dir", I think I personally prefer it to "Exclude Flag
> File", which w
Would it be too difficult to make this file work like .cvsignore
instead of just ignoring the current folder and its children? I can
see this being a lot more flexible but more difficult in
implementation and usage.
http://glast-ground.slac.stanford.edu/workbook/pages/cmtMRvcmt/defCvsignoreFiles.h
* Kern Sibbald schrieb am 04.10.08 um 16:26 Uhr:
> Hello Marc,
Hello Kern,
>
> I am sorry, but from what you wrote below, I really am not sure what you like
> and what you do not like.
I did not want to confuse you ;)
I assumed that things like WildDir work in Include as well as in
Exclude sec
Hello,
This is just to warn you that I have refactored a part of the restore code,
and it is not yet tested enough to know if it is stable or not.
A couple of days of regression tests on various platforms should let us know.
Best regards,
Kern
-
I had a failed attempt to take the build using mingw-w64 for windows 64
(respecting kern's intention to stick to linux for taking windows builds)before
falling back to windows and visual studio..
May be because I was more familiar with windows and visual studio..
Somebody more familiar with mingw
On Thursday 25 September 2008 16:10:47 Josh Fisher wrote:
> Kern Sibbald wrote:
> > Hello,
> >
> > On Thursday 25 September 2008 12:09:11 Riyas Y. wrote:
> >
> > ...
> >
> >> In the latest Bacula source code the Visual Studio Configuration has
> >> fallen out of sync and taking a 64 bit build in wi
Hello Marc,
I am sorry, but from what you wrote below, I really am not sure what you like
and what you do not like.
There are two things that need to be decided separately:
1. Where to place the directive
- Options section
- Include section
- Exclude section
2. The name of the opti
* Kern Sibbald schrieb am 04.10.08 um 15:13 Uhr:
> Hello,
>
> Thanks for your comments.
>
> I think the best suggestion that I have seen for the name is (at least in the
> current context):
>
> Exclude Dirs Containing = .no_backup
I though about this too, but then discarded the idea beacuse I
Hello,
Thanks for your comments.
I think the best suggestion that I have seen for the name is (at least in the
current context):
Exclude Dirs Containing = .no_backup
That seems to me to be a very good name.
Concerning the placement of the directive: I think it is worth examining if we
can ea
* Dan Langille schrieb am 03.10.08 um 21:15 Uhr:
>
>
> I see what you mean. The directive is: Ignore Dir =
>
> So at a minimum, it should be Ignore Dir File =
>
> But having Dir and File together... no.
ACK
>
> Taking the example at:
> http://www.bacula.org/manuals/en/concepts/concepts/N
39 matches
Mail list logo
