[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bacula-devel
Subject:    Re: [Bacula-devel] backup levels - Base not used for future diffs
From:       Kern Sibbald <kern () sibbald ! com>
Date:       2008-02-22 14:27:56
Message-ID: 200802221527.56904.kern () sibbald ! com
[Download RAW message or body]

On Friday 22 February 2008 14.38:51 Dan Langille wrote:
> Ralf Gross wrote:
> > Kern Sibbald schrieb:
> >> On Monday 18 February 2008 16.42:49 Dan Langille wrote:
> >>> This was reported to me on IRC
> >>>
> >>> If you run a BASE level job, it is actually run as a FULL.
> >>>
> >>> However, that FULL will not be recognized by a DIFF job.  The DIFF
> >>> job will use a previous FULL, not the one run as a BASE.
> >>>
> >>> Is this intended/accidental/expected?
> >>
> >> Base code is not implemented nor documented, so I recommend not using
> >> it.
> >
> > Wouldn't it be good idea to remove commands that are not (yet)
> > implemented from the options bconsole show?
>
> If agreed, I'll volunteer to comment out the code.

Yes, no problem.  You just need to try to find a way so that it doesn't 
inadvertently make existing Bacula scripting fail.  Probably the best way is 
not to remove the item, but simply print an error message if it is selected 
unless you can find a way to guarentee that scripting won't be broken (i.e. 
that the index input does not change).

Kern



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
[prev in list] [next in list] [prev in thread] [next in thread]