]> git.sur5r.net Git - bacula/bacula/commit
Force the re-initialization of BaseJobOpts, AccurateOpts and VerifyOpts between two...
authorEric Bollengier <eric@baculasystems.com>
Sat, 10 Mar 2012 09:25:15 +0000 (10:25 +0100)
committerKern Sibbald <kern@sibbald.com>
Sat, 20 Apr 2013 12:50:33 +0000 (14:50 +0200)
commit40d22174ddaa17eb3ddd007707066544c481d863
tree11d446df348e8a3b0ccbb1e0ea45d13ca697172e
parent55905ae035c8c289d2f540bf8d853ec5f486d2d7
Force the re-initialization of BaseJobOpts, AccurateOpts and VerifyOpts between two Include{}

When using this configuration

FileSet {
 Name = X
 Include {
   Options { Accurate = A }
   File = /tmp
 }

 Include {
   Options { Compression = GZIP1 }
   File = /elsewhere
 }
}

The second Include {} block is using the Accurate=A option from the first Include{}. With this
fix, the Accurate/BaseJob/Verify options are set to default between two Include{}.

We still have the same kind of problem for the "flags" that contains most options.
Something like the following configuration won't work as expected:

FileSet {
 Name = X
 Include {
   Options { Portable = no }
   File = /tmp
 }

 Include {
   Options { Portable = yes }
   File = /elsewhere
 }
}
bacula/src/findlib/find.c