> Well, I'm not categorically stating that you have to. That was just my
> surmise as to how it's little brain works. I mean, for example, if I
> list say / under the savesets for a given client then is NetWorker gonna
> back up just / or is it gonna back up all the file systems? Of course,
> we all know it will descend no further than /; so, with the exception of
> the mount point path names, any other file systems would not be captured
> even though their mount points are under the root FS. I guess I was
> thinking that directives would follow along the same logic?
> 
> But I would try it, and if doing it that way works ... natch. Should be
> easy enough to test. As far as it being a bummer ... yes, it is. Might
> be something in the man page, though, for uasm that might tell you how
> to work around it?

The language in nsr(5) leads me to believe that it should traverse
filesystems.  The language about the .nsr files is explicit that it does
do so.  I see no reason that the server-fed directives would not also.


-- 
Darren Dunham                                           ddunham AT taos DOT com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=