fuser displays the process IDs of the processes that are using the files specified as arguments.
Each process ID is followed by a letter code. These letter codes are interpreted as follows: if the process is using the file as
Indicates that the process is using the file as its current directory.
Indicates that the process is using the file as an open file.
Indicates that the process is using the file as its root directory.
Indicates that the process is using the file as its text file.
Indicates that the process is using the file as its controlling terminal.
For block special devices with mounted file systems, all processes using any file on that device are listed. For all types of files (text files, executables, directories, devices, and so forth), only the processes using that file are reported.
If more than one group of files are specified, the options may be respecified for each additional group of files. A lone dash cancels the options currently in force.
The process IDs are printed as a single line on the standard output, separated by spaces and terminated with a single new line. All other output is written on standard error.
Any user can run fuser, but only the superuser can terminate another user's process.
The following options are supported:
Reports on files that are mount points for file systems, and any files within that mounted file system.
Print a report for the named file, not for files within a mounted file system.
SIGKILL signal to each process. Since this option spawns kills for each process, the kill
messages may not show up immediately (see kill(2)).
Displays the user login name in parentheses following the process ID.
See environ(5) for descriptions of the following environment variables that affect the execution of fuser: LANG, LC_ALL LC_CTYPE, LC_MESSAGES, and NLSPATH.
See attributes(5) for descriptions of the following attributes:
|ATTRIBUTE TYPE||ATTRIBUTE VALUE|
Because fuser works with a snapshot of the system image, it may miss processes that begin using a file while fuser is running. Also, processes reported as using a file may have stopped using it while fuser was running. These factors should discourage the use of the -k option.