Re: [Networker] directive to include certain file regex

In regard to: Re: [Networker] directive to include certain file regex, A...:

A +skipped directory isn't descended, so none of
the children can match.


Is that really true?  I was always under the impression that even with
+skip, NetWorker did still descend into directories for one reason: to see
if there were any later directives that countermanded the skip (namely,
"forget").

The uasm(8) man page's coverage of +skip seems to strongly support your
explanation, but nsr(5)'s explanation of the algorithm for applying ASMs
doesn't appear to agree with uasm(8)'s explanation of +skip.

For the original poster: if you're really determined, one possibility you
could try is generating your .nsr file on the fly and creating it so that
each of the files is matched by an asm that does *not* begin with a + and
is listed earlier in the .nsr file than the +skip.  If you follow the
explanation of the algorithm in nsr(5), it seems like something like

<< /path/to/file/one >>
        allow: exact_file1_name_here exact_file2_name_here
<< /path/to/file/three >>
        allow: exact_file3_name_here exact_file4_name_here
<< . >>
        +skip:  * .?*

*might* work (I'm skeptical at this point, but it might be worth a try).
If that doesn't, you would have to do some very complicated scripting to
generate multiple .nsr files to accomplish what you want.  It's possible
if you're really, really desperate, but not for the faint of heart.

Tim
--
Tim Mooney                                             Tim.Mooney AT ndsu DOT 
edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, IACC Building                             701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the body of the email. Please write to networker-request 
AT listserv.temple DOT edu if you have any problems with this list. You can access the 
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER