On Thu, 2007-11-01 at 19:56 +0000, Martin Simmons wrote:
> >>>>> On Wed, 31 Oct 2007 22:50:02 -0400, Brian A Seklecki (Mobile) said:
> >
> > Per the doc excerpt below, I read this to mean:
> >
> > "First Matching Rule Stops Further Evaluation".
> >
> > Then, per the example below the except below regarding:
> >
> > [...snip...]
> > wildfile = "*.Z"
> > wildfile = "*.gz"
> >
Bill and I were just going over an odd problem:
Is it possible that the FD goes through two entirely separate loops
though the file-system hierarchy?
- One for directories...
- A second one for Files?
It first
- traverses the "File=/foo" hierarchies for directories (a la:
"#find /foo -type d")
- Applies any Include/Exclude Options {}, using "First Match Stops
Evaluation" algorithm
- Any RegexDir matches preclude certain sub-directory hierarchies
- Caches that list
Second:
- Uses the cached directories hierarchy
- Descends into each directory (a la "find /foo -type f")
- Applies any RegexFile Include/Exclude Options{}'s using "First
Match Stops Evaluation" algorithm
Does this sound plausible? That would explain a strange we've been
having with order-of-evaluation on a complex include/exclude set.
~BAS
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
