1
2FEDFS-DELETE-REPLICATION(8) System Manager's ManualFEDFS-DELETE-REPLICATION(8)
3
4
5

NAME

7       fedfs-delete-replication - send a FEDFS_DELETE_REPLICATION ADMIN proto‐
8       col request
9

SYNOPSIS

11       fedfs-delete-replication [-?d] [-n nettype] [-h hostname] [-s security]
12       path
13

INTRODUCTION

15       RFC  5716  introduces  the  Federated  File  System (FedFS, for short).
16       FedFS is an extensible standardized mechanism by which system  adminis‐
17       trators  construct  a  coherent  namespace across multiple file servers
18       using file system referrals.  For further details, see fedfs(7).
19
20       FedFS-enabled file servers allow remote administrative  access  via  an
21       authenticated  RPC  protocol  known as the FedFS ADMIN protocol.  Using
22       this protocol, FedFS administrators manage  FedFS  junctions  and  NSDB
23       connection parameter information on remote FedFS-enabled file servers.
24

DESCRIPTION

26       The fedfs-delete-replication(8) command is part of a collection of low-
27       level single-use programs that is intended for testing the FedFS  ADMIN
28       protocol  or for use in scripts.  It sends a single FEDFS_DELETE_REPLI‐
29       CATION request to a remote FedFS ADMIN protocol service.
30
31       The FEDFS_DELETE_REPLICATION request deletes a replication marker in  a
32       local  file  system on a remote file server.  The fedfs-delete-replica‐
33       tion(8) command taks a single positional parameter which is  the  path‐
34       name  on  the  remote  server  of the replication marker to be deleted.
35       This pathname is relative to the root of the local file system  on  the
36       remote server.
37

OPTIONS

39       -d, --debug
40              Enables debugging messages during operation.
41
42       -?, --help
43              Displays  fedfs-delete-replication(8)  version information and a
44              usage message on stderr.
45
46       -h, --hostname=hostname
47              Specifies the hostname of a remote FedFS ADMIN service.  If this
48              option is not specified, the default value is localhost.
49
50       -n, --nettype=nettype
51              Specifies  the transport to use when contacting the remote FedFS
52              ADMIN service.  Typically the nettype is one of tcp or udp.   If
53              this option is not specified, the default value is netpath.  See
54              rpc(3t) for details.
55
56       -s, --security=flavor
57              Specifies the security flavor to use when contacting the  remote
58              FedFS  ADMIN service.  Valid flavors are sys, unix, krb5, krb5i,
59              and krb5p.  If this option is not specified, the unix flavor  is
60              used.  See the SECURITY section of this man page for details.
61

EXAMPLES

63       Suppose  you  are  the  FedFS  administrator  of  the example.net FedFS
64       domain.  To delete an existing FedFS replication on the  remote  server
65       fs.example.net, use:
66
67              $  fedfs-delete-replication  -h  fs.example.net /export/replica‐
68              tion1
69

SECURITY

71       By default, or if the sys and  unix  flavors  are  specified  with  the
72       --security=flavor  option,  the  fedfs-create-junction(8)  command uses
73       AUTH_SYS security for the Remote Procedure Call.   AUTH_SYS  has  known
74       weaknesses and should be avoided on untrusted networks.
75
76       The  RPC  client uses the Kerberos v5 GSS mechanism if a Kerberos secu‐
77       rity flavor is specified.  When specifying a Kerberos security  flavor,
78       the  user  must  first  obtain  a  valid Kerberos ticket using kinit(1)
79       before running fedfs-create-junction(8).
80
81       The AUTH_NONE security flavor is no longer supported by this  implemen‐
82       tation.
83

SEE ALSO

85       fedfs(7), rpc.fedfsd(8), kinit(1), rpc(3t)
86
87       RFC 5716 for FedFS requirements and overview
88

COLOPHON

90       This  page  is  part  of the fedfs-utils package.  A description of the
91       project  and  information  about  reporting  bugs  can  be   found   at
92       http://wiki.linux-nfs.org/wiki/index.php/FedFsUtilsProject.
93

AUTHOR

95       Chuck Lever <chuck.lever@oracle.com>
96
97
98
99                                3 February 2014    FEDFS-DELETE-REPLICATION(8)
Impressum