Previous section.

Protocols for Interworking: XNFS, Version 3W
Copyright © 1998 The Open Group


NFSPROC_READLINK - Read From Symbolic Link

Call Arguments

typedef opaque fhandle[NFS_FHSIZE];

Return Arguments

union readlinkres switch (stat status) { case NFS_OK: path data; default: void; };

path and sattr are defined in Basic Data Types .

RPC Procedure Description

readlinkres NFSPROC_READLINK(fhandle) = 5;


If status has the value NFS_OK, then the reply data is the data in the symbolic link given by the file referred to by the fhandle argument. The file handle supplied to this procedure must refer to a file of the symbolic link file type.

An NFS server need not implement symbolic links; if it does not, it will return a PROC_UNAVAIL error. An NFS client should only issue an NFSPROC_READLINK if a lookup returns an entry that is typed as NFLNK, and must be prepared to handle failures of any symbolic link operation.

Note that since NFS always parses pathnames on the client, the pathname in a symbolic link may mean something different (or be meaningless) on a different client or on the server if a different pathname syntax is used.

Return Codes

Indicates that the call completed successfully and the results are valid.

Some sort of hard error occurred when the operation was in progress. This could be a disk error, for example.

The fhandle given in the arguments was invalid. That is, the file referred to by that file handle no longer exists, or access to it has been revoked.

This procedure is not supported.

The fhandle given in the argument does not refer to a symbolic link.

Why not acquire a nicely bound hard copy?
Click here to return to the publication details or order a copy of this publication.

Contents Next section Index