Kern,
Is there anyway to know when this modification
was made?
We've been playing with 1.37.38, and I'm a little
scared to put it into production, so I was
wondering if there was any way to apply this
spool space patch, and possibly the patch
to reduce the number of SQL queries (the
modification that adds the MD5 into the
attributes record), to the 1.36
release?
Were these large, application wide changes? or
just reletively small things that could be
worked into the current stable
version?
Thanks for your help,
Cheers,
Mike Pultz
> ----- Original Message -----
> From: "Kern Sibbald" <[EMAIL PROTECTED]>
> To: <[email protected]>
> Cc: "Robert Westendorp" <[EMAIL PROTECTED]>
> Sent: Tuesday, September 06, 2005 12:21 PM
> Subject: Re: [Bacula-users] "Maximum Job Spool Size" doesn't appear to work
>
>
>> On Tuesday 06 September 2005 19:17, Robert Westendorp wrote:
>> > Hi,
>> >
>> > I'm running some tests of concurrent backups and will want to use data
>> > spooling.
>> >
>> > In my bacula-sd.conf for each device I specify
>> >
>> > Maximum Spool Size = 6g
>> > Maximum Job Spool Size = 2g
>> >
>> > I then run two jobs for two different clients against the above device
> at
>> > the same time.
>> >
>> > The spool file size doesn't stop at the job spool limit .. it stops at
> the
>> > overall spool size. I've also tried this by running a single job and the
>> > same thing happens.
>> >
>> > Am I missing something?
>>
>> If I remember right, I made a silly mistake when comparing the values and
> used
>> the Max Spool size in both tests rather than the Max Spool size and the
> Max
>> Job size. Bottom line Max Job size doesn't work in 1.36 but *should* in
>> 1.37.
>>
>> >
>> > Robert.
>>
>
