Connected: An Internet Encyclopedia
RFC 1813 - 4.6 File name component handling

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1813
Up: 4. Implementation issues
Prev: 4.5 Duplicate request cache
Next: 4.7 Synchronous modifying operations

### 4.6 File name component handling

Server implementations of NFS version 3 protocol will frequently impose restrictions on the names which can be created. Many servers will also forbid the use of names that contain certain characters, such as the path component separator used by the server operating system. For example, the UFS file system will reject a name which contains "/", while "." and ".." are distinguished in UFS, and may not be specified as the name when creating a file system object. The exact error status values return for these errors is specified in the description of each procedure argument. The values (which conform to NFS version 2 protocol server practice) are not necessarily obvious, nor are they consistent from one procedure to the next.

Next: 4.7 Synchronous modifying operations

Connected: An Internet Encyclopedia
RFC 1813 - 4.6 File name component handling