MirOS Manual: getfh(2)

GETFH(2)                   BSD Programmer's Manual                    GETFH(2)

NAME

     getfh - get file handle

SYNOPSIS

     #include <sys/param.h>
     #include <sys/mount.h>

     int
     getfh(const char *path, fhandle_t *fhp);

DESCRIPTION

     getfh() 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 su-
     peruser.

RETURN VALUES

     Upon successful completion, a value of 0 is returned. Otherwise, -1 is
     returned and the global variable errno is set to indicate the error.

ERRORS

     getfh() 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} char-
                   acters, or the length of path exceeds {PATH_MAX} charac-
                   ters.

     [ENOENT]      The file referred to by path does not exist.

     [EACCES]      Search permission is denied for a component of the path
                   prefix of path.

     [ELOOP]       Too many symbolic links were encountered in translating
                   path.

     [EPERM]       The effective user ID is not the superuser.

     [EFAULT]      fhp or path points to an invalid address.

     [EIO]         An I/O error occurred while reading from or writing to the
                   file system.

HISTORY

     The getfh() function first appeared in 4.4BSD.

MirOS BSD #10-current            June 9, 1993                                1

Generated on 2014-04-02 20:57:59 by $MirOS: src/scripts/roff2htm,v 1.79 2014/02/10 00:36:11 tg Exp $

These manual pages and other documentation are copyrighted by their respective writers; their source is available at our CVSweb, AnonCVS, and other mirrors. The rest is Copyright © 2002‒2014 The MirOS Project, Germany.
This product includes material provided by Thorsten Glaser.

This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report – diffs preferred.