*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->FreeBSD man pages              
Title
Content
Arch
Section
 
 VOP_INACTIVE(9) -- reclaim file system resources for a vnode
    The arguments are: vp the vnode being reclaimed VOP_INACTIVE() is called when the kernel is no longer using the vnode. This may be because the reference count reaches zero or it may be that the file s...
 VOP_IOCTL(9) -- device specific control
    Manipulate a file in device dependent ways. Its arguments are: vp the vnode of the file (normally representing a device) command the device specific operation to perform cnp extra data for the specifi...
 VOP_ISLOCKED(9) -- serialize access to a vnode
    These calls are used to serialize access to the file system, such as to prevent two writes to the same file from happening at the same time. The arguments are: vp the vnode being locked or unlocked fl...
 VOP_LEASE(9) -- validate a vnode for a particular set of credentials and operation type
    This entry point is currently not implemented. The idea is to validate a vnode for a particular set of user credentials and operation type. The two operation types supported are LEASE_READ and LEASE_W...
 VOP_LINK(9) -- create a new name for a file
    This links a new name in the specified directory to an existing file. Its arguments are: dvp the vnode of the directory vp the vnode of the file to be linked cnp pathname information about the file Th...
 VOP_LISTEXTATTR(9) -- retrieve a list of named extended attribute from a vnode
    This vnode call may be used to retrieve a list of named extended attributes from a specified namespace on a file or directory. Its arguments are: vp the vnode of the file or directory attrnamespace in...
 VOP_LOCK(9) -- serialize access to a vnode
    These calls are used to serialize access to the file system, such as to prevent two writes to the same file from happening at the same time. The arguments are: vp the vnode being locked or unlocked fl...
 VOP_LOOKUP(9) -- lookup a component of a pathname
    This entry point looks up a single pathname component in a given directory. Its arguments are: dvp the locked vnode of the directory to search vpp the address of a variable where the resulting locked ...
 VOP_MKDIR(9) -- create a file, socket, fifo, device, directory or symlink
    These entry points create a new file, socket, fifo, device, directory or symlink in a given directory. The arguments are: dvp the locked vnode of the directory vpp the address of a variable where the ...
 VOP_MKNOD(9) -- create a file, socket, fifo, device, directory or symlink
    These entry points create a new file, socket, fifo, device, directory or symlink in a given directory. The arguments are: dvp the locked vnode of the directory vpp the address of a variable where the ...
 VOP_OPEN(9) -- open or close a file
    The VOP_OPEN() entry point is called before a file is accessed by a process and the VOP_CLOSE() entry point is called after a file is finished with by the process. The arguments are: vp the vnode of t...
 VOP_OPENCLOSE(9) -- open or close a file
    The VOP_OPEN() entry point is called before a file is accessed by a process and the VOP_CLOSE() entry point is called after a file is finished with by the process. The arguments are: vp the vnode of t...
 VOP_PATHCONF(9) -- return POSIX pathconf information
    The arguments are: vp the vnode to get information about name the type of information to return retval the place to return the information The value of name specifies what should be returned: _PC_LINK...
 VOP_PRINT(9) -- print debugging information
    The arguments are: vp the vnode to print
 VOP_PUTPAGES(9) -- read or write VM pages from a file
    The VOP_GETPAGES() method is called to read in pages of virtual memory which are backed by ordinary files. If other adjacent pages are backed by adjacent regions of the same file, VOP_GETPAGES() is re...
<<  [Prev]  31  32  33  34  35  36  37  38  39  40  41  42  43  44  45  46  47  48  49  50  51  
52  53  [Next]  >>
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service