Kern Sibbald wrote:
> On Monday 28 November 2005 19:38, Martin Simmons wrote:
>
>>>>>>> On Mon, 28 Nov 2005 17:06:00 +0100, Kern Sibbald <[EMAIL PROTECTED]>
>>>>>>> said:
>>
>>
>> Kern> On Monday 28 November 2005 15:55, Martin Simmons wrote:
>> >> >>>>> On Fri, 25 Nov 2005 09:21:29 +0000, Greg Cope
>> >> >>>>> <[EMAIL PROTECTED]> said:
>>
>> Greg> I am trying to glob a load of oracle backup files. As per Stephan
>> Greg> Ebelt's post these will be under /uNN dirs that are often on
>>
>> >> different Greg> file systems.
>>
>> Greg> What I am trying to do is;
>>
>> Greg> regex = "^\/u[0-9]{2}\/(oraback|oraarch)"
>>
>> Greg> But the following fail to match anything bar '/'
>>
>> Greg> regex = "^\/u[0-9]{2}\/(oraback|oraarch)"
>> Greg> regex = "^\/u[0-9]{2}\/oraexp"
>> Greg> regex = "^\/u[0-9]{2}\/oraback"
>> Greg> regex = "^\/u[0-9]{2}.oraback"
>>
>> Greg> As expected regex = "^\/u[0-9]{2}" matches the lot.
>>
>> Greg> Can anyone shed any light on this or the regex code?
>>
>> >> The problem is that Bacula walks down the tree of directories looking
>> >> for matching include/exclude patterns. When it finds an excluded
>> >> directory, it doesn't look any deeper in that directory. Now /u02
>> >> doesn't match any of the above, so it stops the walk before
>> >> /u02/oraback is found.
>> >>
>> >> BTW, I don't think you need \ before / in a regex.
>>
>> Kern> Recently, I added something similar to this example to the FileSet
>> chapter of Kern> the manual. It would be interesting to know what you
>> think about the example Kern> Martin since I haven't actually "run" it. Of
>> course, the example doesn't Kern> deal with more complex issues such as
>> traversing subdirectories where parents Kern> may be excluded ...
>>
>> I found the new examples, but what the ^.?*$ is "^.?*$" supposed to mean?
If we are talking about extended regexp "^.?*$" indeed is a sytax error. There
must be something in front of the *. You could say "^.?.*$" but this is the
same as "^.*$".
>
> Match the whole line no matter what it contains. .* doesn't seem to work on
Linux ...
Mhh if it doesn't work you're using basic regular expressions. (And it means
a line containing any number of dots) And then "^.?*$" works and means the
same as "^*$".
> I'll take another look at it.
>
>
>> :-) As the manual mentions in a previous example, this regexp doesn't
>> compile on FreeBSD, so the example won't work. Maybe you just want ".*",
>> i.e. match anything?
>>
>> __Martin
>
>
>
--
Mit freundlichen Grüßen
Attila Fülöp
Netzwerkadministrator
__________________________________________________________
BSMO GmbH
Johannisberger Straße 74, D-14197 Berlin
Postfach 140201, D-14302 Berlin
Telefon +49(30) 884 293 - 14
Telefax +49(30) 884 293 - 41
Mobile +49(172) 384 27 29
E-Mail mailto:[EMAIL PROTECTED]
-----------------------------------------------------------
Medizin und Gesundheit im Internet
http://www.bsmo.de
http://www.lifeline.de
http://www.multimedica.de
-----------------------------------------------------------
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
