Re: [Bacula-users] Problems after Update

[pete c. <li...@za...>]

Kern Sibbald wrote:

> The output you see is debug output. If I remember right I released a
> patch to suppress it. In any case I will be releasing 1.34.1 very
> shortly (beginning of the week) where it is fixed.
> 
> Best regards, Kern 
> 

> On Sun, 2004-04-18 at 16:28, Norm Dressler wrote:
>>I have another question too -- I'm now seeing things like the following in my 
>>logs that I didn't see before:
>>
>>18-Apr-2004 10:19 manager-sd: 3305 Autochanger "load slot 1, drive 0", status 
>>is OK.
>>18-Apr-2004 10:19 manager-dir: sql_update.c:348 UPDATE Media SET InChanger=0 
>>WHERE PoolId=1 AND Slot=1 AND MediaId!=1
>>18-Apr-2004 10:19 manager-sd: Wrote label to prelabeled Volume "DIN009" on 
>>device "/dev/st0"
>>18-Apr-2004 10:21 manager-dir: sql_update.c:348 UPDATE Media SET InChanger=0 
>>WHERE PoolId=1 AND Slot=1 AND MediaId!=1
>>
>>The sql statement at the end is what I'm referring too...
>>
>>Is this a new feature or debug code left in or what?
>>
>>Thanks
>>Norm

hi

great program, now that my patched freebsd has passed tapetest :)

still seem to be getting the debug statements in the e-mailed report for 
ver 1.34.2:

jenny-dir: sql_update.c:348 UPDATE Media SET InChanger=0 WHERE PoolId=1 
AND Slot=1 AND MediaId!=32
jenny-dir: Bacula 1.34.2 (24Apr04): 28-Apr-2004 10:27

ok to just comment it out in the source? thanx.

pete