Hi Stan,
Why not use this one:
<< /dev >>
+skip: .?*
<< /usr/local/perlmx >>
+skip: .?*
Also just have a look on your client, if there isn't a local directive =
which wipes the globel ones out. .
regards
Klaus
-----Urspr=FCngliche Nachricht-----
Von: Legato NetWorker discussion=20
[mailto:NETWORKER < at > LISTMAIL.TEMPLE.EDU] Im Auftrag von Stan Horwitz
Gesendet: Mittwoch, 22. September 2004 15:57
An: NETWORKER < at > LISTMAIL.TEMPLE.EDU
Betreff: [Networker] Problem with a directive file
=20
=20
The NetWorker server in question is Power Edition NetWorker 7.1.2 on
a Sunfire v480 with Solaris 9. The client in question is=20
running NetWorker
6.1.2 on a Suse Linux system.
=20
The problem is that directives on this particular client are=20
ignored. When
I try to run a probe or server initiated backup of this=20
client, it looks
like everything gets backed up. I have tried several permutations of
directives and tried both server side and client side=20
directives, but both
are ignored.
=20
What I want to do is avoid ever backing up the /dev and=20
/usr/local/perlmx
directories. I have tried things like putting a .nsr file in the root
directory that looks like:
=20
<< / >>
skip: dev
<< /usr/local >>
skip: perlmx
=20
but each time I try to back up that Linux server, it attempts=20
to back up
the /usr/local/perlmx and /dev directories too. Directives I=20
have on other
servers are working fine, but not on this server.
=20
What am I doing wrong?
=20
--
Note: To sign off this list, send a "signoff networker"=20
command via email
=
=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D=
*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D
=20
Note: To sign off this list, send a "signoff networker" command via email
=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D*=3D
