Connected: An Internet Encyclopedia
RFC 1813 - 5.2.1 Procedure 1: MNT - Add mount entry

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1813
Up: 5. Appendix I: Mount protocol
Up: 5.2 Server Procedures
Prev: 5.2.0 Procedure 0: Null - Do nothing
Next: 5.2.2 Procedure 2: DUMP - Return mount entries

### 5.2.1 Procedure 1: MNT - Add mount entry

SYNOPSIS

            mountres3 MOUNTPROC3_MNT(dirpath) = 1;

            struct mountres3_ok {
                 fhandle3   fhandle;
                 int        auth_flavors<>;
            };

            union mountres3 switch (mountstat3 fhs_status) {
            case MNT_OK:
                 mountres3_ok  mountinfo;
            default:
                 void;
            };

DESCRIPTION

  Procedure MNT maps a pathname on the server to a file handle. The pathname is an ASCII string that describes a directory on the server. If the call is successful (MNT3_OK), the server returns an NFS version 3 protocol file handle and a vector of RPC authentication flavors that are supported with the client's use of the file handle (or any file handles derived from it). The authentication flavors are defined in Section 7.2 and section 9 of [RFC1057].

IMPLEMENTATION

  If mountres3.fhs_status is MNT3_OK, then mountres3.mountinfo contains the file handle for the directory and a list of acceptable authentication flavors. This file handle may only be used in the NFS version 3 protocol. This procedure also results in the server adding a new entry to its mount list recording that this client has mounted the directory. AUTH_UNIX authentication or better is required.

ERRORS

  MNT3ERR_NOENT MNT3ERR_IO MNT3ERR_ACCES MNT3ERR_NOTDIR MNT3ERR_NAMETOOLONG

Next: 5.2.2 Procedure 2: DUMP - Return mount entries

Connected: An Internet Encyclopedia
RFC 1813 - 5.2.1 Procedure 1: MNT - Add mount entry