On 11/27/06, Erich Prinz <[EMAIL PROTECTED]> wrote:
Thanks Martin, that got it.
So yes, running 1.36.x on OS X 10.4.x shows that large file support
is enabled.
Erich
Thanks Erich (and all others) for beating me to the punch and solving this
question. Its a good one to solve with certainty a
Thanks Martin, that got it.
So yes, running 1.36.x on OS X 10.4.x shows that large file support
is enabled.
Erich
On Nov 27, 2006, at 2:15 PM, Martin Simmons wrote:
>> On Mon, 27 Nov 2006 07:50:48 -0600, Erich Prinz said:
>>
>>
>>
>> running a status in bconsole (even with -dnn) doesn't
On Monday 27 November 2006 14:50, Erich Prinz wrote:
>
>
>
> running a status in bconsole (even with -dnn) doesn't yield the
> output you suggest below. Likely a nuance with BSD.
No all daemons use the same code. Most likely on pre 1.39 you must set a
debug level on the FD of say 10.
>
>
On 11/27/06, Erich Prinz <[EMAIL PROTECTED]> wrote:
Running 10.4.8 on this end.
What I can do is run a job with a large file and let you know the
results. The configure options in the previous post don't included
that option and per Kern's post on the subject, it appears it is on
by default (wh
On 11/26/06, Kern Sibbald <[EMAIL PROTECTED]> wrote:
On Monday 27 November 2006 05:16, Hydro Meteor wrote:
SNIP
On the Mac, configure reported a value of "no" assigned as in:
>
> Large file support: no
If MacOS X is derived from FreeBSD, as I believe it is, this is "normal"
in
the sens
> On Mon, 27 Nov 2006 07:50:48 -0600, Erich Prinz said:
>
>
>
> running a status in bconsole (even with -dnn) doesn't yield the
> output you suggest below. Likely a nuance with BSD.
Older versions of Bacula only report the sizes for debug>0, so try doing this
first:
setdebug client level
Running 10.4.8 on this end.
What I can do is run a job with a large file and let you know the
results. The configure options in the previous post don't included
that option and per Kern's post on the subject, it appears it is on
by default (which would make sense for Apple to do given the he
running a status in bconsole (even with -dnn) doesn't yield the
output you suggest below. Likely a nuance with BSD.
>
> You can check if a particular client has large file support despite
> what the
> configure output says by doing a:
>
> status client=xxx
>
> in the console. If you get
On Monday 27 November 2006 05:16, Hydro Meteor wrote:
> Hello,
>
> I was able to ./configure Bacula 1.38.11 on a Mac running Mac OS X
> 10.4.8without any problems today (in a manner almost exactly the same
> as my Ubuntu
> Linux configuration). In both cases, I did not explicitly provide configure
On 11/26/06, Erich Prinz <[EMAIL PROTECTED]> wrote:
Can't help on this one. PPC only on this end.
Hi Erich,
A Bacula News Bulletin just in ... I just moments ago tried on Mac OS X
Server 10.4.8 running on a PowerPC Mac, the exact same configure options on
the same original source of Bacula (
Can't help on this one. PPC only on this end.
Odd that it was explicit in the configure options but not found when
running.
Have you attempted to run a backup on a single file over 2 GB just to
see what would happen? Just curious.
Erich
On Nov 26, 2006, at 10:30 PM, Hydro Meteor wrote:
>
As a followup I have copied and pasted what appears to be a relevant section
of my config.log output on the same iMac which I tried to enable large file
support for. If anyone who is more familiar with the inner workings of
Bacula (Kern?) could shed some additional light on what would be a good ne
Hello,
I was able to ./configure Bacula 1.38.11 on a Mac running Mac OS X
10.4.8without any problems today (in a manner almost exactly the same
as my Ubuntu
Linux configuration). In both cases, I did not explicitly provide configure
with the option of disabling large file support, and I also did
13 matches
Mail list logo
