Query: getfh
OS: osx
Section: 2
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
GETFH(2) BSD System Calls Manual GETFH(2)NAMEgetfh -- get file handleSYNOPSIS#include <sys/types.h> #include <sys/mount.h> int getfh(const char *path, fhandle_t *fhp);DESCRIPTIONGetfh() returns a file handle for the specified file or directory in the file handle pointed to by fhp. This system call is restricted to the super-user and is used by an NFS server's nfsd(8) daemon to obtain file handles used in NFS MOUNT service replies.RETURN VALUESUpon successful completion, a value of 0 is returned. Otherwise, -1 is returned and the global variable errno is set to indicate the error.ERRORSGetfh() fails if one or more of the following are true: [ENOTDIR] A component of the path prefix of path is not a directory. [ENAMETOOLONG] The length of a component of path exceeds {NAME_MAX} characters, or the length of path exceeds {PATH_MAX} characters. [ENOENT] The file referred to by path does not exist. [EPERM] The caller is not the super-user. [EACCES] Search permission is denied for a component of the path prefix of path. [ELOOP] Too many symbolic links were encountered in translating path. [EFAULT] Fhp points to an invalid address. [EIO] An I/O error occurred while reading from or writing to the file system.SEE ALSOnfsd(8)HISTORYThe getfh() function first appeared in 4.4BSD.BSDJanuary 9, 2007 BSD
Related Man Pages |
---|
getfh(2) - mojave |
fstatvfs1(2) - netbsd |
fstatvfs(2) - netbsd |
resolvepath(2) - sunos |
getfh(2) - freebsd |
Similar Topics in the Unix Linux Community |
---|
How to read the output of snoop command? |
NFS with a NAS: permanently inconsistent directory state across clients |
NFSd problem |