fedfs-null(8)

1
2FEDFS-NULL(8)               System Manager's Manual              FEDFS-NULL(8)
3
4
5

NAME

7       fedfs-null - send a FEDFS_NULL ADMIN protocol request
8

SYNOPSIS

10       fedfs-null [-?d] [-n nettype] [-h hostname] [-s security]
11

INTRODUCTION

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

DESCRIPTION

24       The  fedfs-null(8) command is part of a collection of low-level single-
25       use programs that is intended for testing the FedFS ADMIN  protocol  or
26       for  use  in scripts.  It sends a single FEDFS_NULL request to a remote
27       FedFS ADMIN protocol service.
28
29       The FEDFS_NULL request performs a simple ping operation that determines
30       if there is an operational FedFS ADMIN service on the remote server.
31

OPTIONS

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

EXAMPLES

57       Suppose you are the FedFS administrator of the example.net FedFS domain
58       and that you want to know if the FedFS ADMIN service on the file server
59       fs.example.net is operational.  Use:
60
61              $ fedfs-null -h fs.example.net
62              Call completed successfully
63

SECURITY

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

COLOPHON

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

AUTHOR

89       Chuck Lever <chuck.lever@oracle.com>
90
91
92
93                                3 February 2014                  FEDFS-NULL(8)