1FEDFS-DELETE-JUNCTION(8) System Manager's Manual FEDFS-DELETE-JUNCTION(8)
3
7 fedfs-delete-junction - send a FEDFS_DELETE_JUNCTION ADMIN protocol
8 request
9
11 fedfs-delete-junction [-?d] [-n nettype] [-h hostname] [-s security]
12 path
13
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 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
26 The fedfs-delete-junction(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_JUNC‐
29 TION request to a remote FedFS ADMIN protocol service.
30 The FEDFS_DELETE_JUNCTION request deletes a FedFS junction in a local
32 file system on a remote file server. The fedfs-delete-junction(8) com‐
33 mand takes a single positional parameter which is the pathname on the
34 remote server of the junction to be deleted. This pathname is relative
35 to the root of the local file system on the remote server.
36 The FEDFS_DELETE_JUNCTION request does not remove the FSN record asso‐
38 ciated with the deleted junction. Other junctions may continue to
39 refer to the FSN in the deleted junction.
40 When no junction refers to this FSN, use the nsdb-delete-fsn(8) command
42 to delete the FSN and children FSL records. Resolving a junction that
43 contains an FSN UUID without a matching FSN record on the NSDB results
44 in an error on the file server.
45
47 -d, --debug
48 Enables debugging messages during operation.
49 -?, --help
51 Displays fedfs-delete-junction(8) version information and a
52 usage message on stderr.
53 -h, --hostname=hostname
55 Specifies the hostname of a remote FedFS ADMIN service. If this
56 option is not specified, the default value is localhost.
57 -n, --nettype=nettype
59 Specifies the transport to use when contacting the remote FedFS
60 ADMIN service. Typically the nettype is one of tcp or udp. If
61 this option is not specified, the default value is netpath. See
62 rpc(3t) for details.
63 -s, --security=flavor
65 Specifies the security flavor to use when contacting the remote
66 FedFS ADMIN service. Valid flavors are sys, unix, krb5, krb5i,
67 and krb5p. If this option is not specified, the unix flavor is
68 used. See the SECURITY section of this man page for details.
69
71 Suppose you are the FedFS administrator of the example.net FedFS
72 domain. To delete the existing FedFS junction /export/junction1 on the
73 file server fs.example.net, use:
74 $ fedfs-delete-junction -h fs.example.net /export/junction1
76
78 By default, or if the sys and unix flavors are specified with the
79 --security=flavor option, the fedfs-create-junction(8) command uses
80 AUTH_SYS security for the Remote Procedure Call. AUTH_SYS has known
81 weaknesses and should be avoided on untrusted networks.
82 The RPC client uses the Kerberos v5 GSS mechanism if a Kerberos secu‐
84 rity flavor is specified. When specifying a Kerberos security flavor,
85 the user must first obtain a valid Kerberos ticket using kinit(1)
86 before running fedfs-create-junction(8).
87 The AUTH_NONE security flavor is no longer supported by this implemen‐
89 tation.
90
92 fedfs(7), rpc.fedfsd(8), kinit(1), rpc(3t)
93 RFC 5716 for FedFS requirements and overview
95
97 This page is part of the fedfs-utils package. A description of the
98 project and information about reporting bugs can be found at
99 http://wiki.linux-nfs.org/wiki/index.php/FedFsUtilsProject.
100
102 Chuck Lever <chuck.lever@oracle.com>
103 3 February 2014 FEDFS-DELETE-JUNCTION(8)