fuser(1) [freebsd man page]
FUSER(1) BSD General Commands Manual FUSER(1) NAME
fuser -- list IDs of all processes that have one or more files open SYNOPSIS
fuser [-cfkmu] [-M core] [-N system] [-s signal] file ... DESCRIPTION
The fuser utility writes to stdout the PIDs of processes that have one or more named files open. For block and character special devices, all processes using files on that device are listed. A file is considered open by a process if it was explicitly opened, is the working directory, root directory, jail root directory, active executable text, kernel trace file or the controlling terminal of the process. If -m option is specified, the fuser utility will also look through mmapped files. The following options are available: -c Treat files as mount point and report on any files open in the file system. -f The report must be only for named files. -k Send signal to reported processes (SIGKILL by default). -m Search through mmapped files too. -u Write the user name associated with each process to stderr. -M Extract values associated with the name list from the specified core instead of the default /dev/kmem. -N Extract the name list from the specified system instead of the default, which is the kernel image the system has booted from. -s Use given signal name instead of default SIGKILL. The following symbols, written to stderr will indicate how files is used: r The file is the root directory of the process. c The file is the current workdir directory of the process. j The file is the jail-root of the process. t The file is the kernel tracing file for the process. x The file is executable text of the process. y The process use this file as its controlling tty. m The file is mmapped. w The file is open for writing. a The file is open as append only (O_APPEND was specified). d The process bypasses fs cache while writing to this file (O_DIRECT was specified). s Shared lock is hold. e Exclusive lock is hold. EXIT STATUS
The fuser utility returns 0 on successful completion and >0 otherwise. EXAMPLES
The command: ``fuser -fu .'' writes to standard output the process IDs of processes that are using the current directory and writes to stderr an indication of how those processes are using the directory and user names associated with the processes that are using this directory. SEE ALSO
fstat(1), ps(1), systat(1), iostat(8), pstat(8), vmstat(8) STANDARDS
The fuser utility is expected to conform to IEEE Std 1003.1-2004 (``POSIX.1''). HISTORY
The fuser utility appeared in FreeBSD 9.0. AUTHORS
The fuser utility and this manual page was written by Stanislav Sedov <stas@FreeBSD.org>. BUGS
Since fuser takes a snapshot of the system, it is only correct for a very short period of time. When working via kvm(3) interface the report will be limited to filesystems the fuser utility knows about (currently only cd9660, devfs, nfs, ntfs, nwfs, udf, ufs and zfs). BSD
May 13, 2011 BSD
Check Out this Related Man Page
fuser(1M) fuser(1M) NAME
fuser - list processes using a file or file structure SYNOPSIS
file ... file ...] ... DESCRIPTION
The command lists the process IDs of processes that have each specified file open. For block special devices, all processes using any file on that device are listed. The process ID may be followed by a letter, identifying how the file is being used, as follows: file is current directory of the process. file is the root directory of the process, as set up by the command (see chroot(1M)). The process has file open. The process has file memory mapped. file is the text file of the process. The process IDs associated with each file are printed to standard output as a single line separated by spaces and terminated with a single newline. All other output -- the file name, the letter, and the user name -- is written to standard error. Options has the following options: Display the use of a mount point and any file beneath that mount point. Each file must be a file system mount point. Display the use of the named file only, not the files beneath it if it is a mounted file system. This is the default. Display the login user name in parentheses following each process ID. Send the signal to each process using each file. You must have appropriate privileges to kill processes that you do not own. You can respecify options between groups of files. The new set of options replaces the old set. A dash by itself cancels all options cur- rently in force. Operands has the following operand: file One of the following values: o With the option, the name of a file. o With the option, the name of a mounted file system or special file. o With the option, the name of a file system mount point. NETWORKING FEATURES
You can use with NFS file systems or files. If the file name is in the format used in to identify an NFS file system, treats the NFS file system as a block special device and identifies any process using that file system. If contact with an NFS file system is lost, fails, since contact is required to obtain the file system identification. Once the NFS file system is recontacted, stale file handles from the previous contact can be identified, provided that the NFS file system has the same file system identification. EXAMPLES
Terminate all processes that are preventing disk drive 1 from being unmounted, listing the process ID and login name of each process being killed. List process IDs and login names of processes that have the password file open. Combine both the above examples into a single command line. If the device is mounted on directory list the process IDs and login names of processes using the device. Alternately, if is the mount point for an NFS file system, list process IDs and login names of processes using that NFS file system. If is an NFS file system, list all processes using any file on that file system. If it is not an NFS file system, treat it as a regular file. SEE ALSO
ps(1), mount(1M), kill(2), signal(2). STANDARDS CONFORMANCE
fuser(1M)