fuser(1m) [hpux 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)

FUSER(1)							   User Commands							  FUSER(1)

NAME

       fuser - identify processes using files or sockets

SYNOPSIS

       fuser [-fuv] [-a|-s] [-4|-6] [-c|-m|-n  space ] [-k [-i] [-w] [-SIGNAL ] ] name ...
       fuser -l
       fuser -V

DESCRIPTION

       fuser displays the PIDs of processes using the specified files or file systems.	In the default display mode, each file name is followed by
       a letter denoting the type of access:

	      c      current directory.

	      e      executable being run.

	      f      open file. f is omitted in default display mode.

	      F      open file for writing. F is omitted in default display mode.

	      r      root directory.

	      m      mmap'ed file or shared library.

       fuser returns a non-zero return code if none of the specified files is accessed or in case of a fatal error. If at  least  one  access  has
       been found, fuser returns zero.

       In  order  to  look  up processes using TCP and UDP sockets, the corresponding name space has to be selected with the -n option. By default
       fuser will look in both IPv6 and IPv4 sockets. To change the default, behavior, use the -4 and -6 options. The socket(s) can  be  specified
       by the local and remote port, and the remote address. All fields are optional, but commas in front of missing fields must be present:

       [lcl_port][,[rmt_host][,[rmt_port]]]

       Either symbolic or numeric values can be used for IP addresses and port numbers.

       fuser outputs only the PIDs to stdout, everything else is sent to stderr.

OPTIONS

       -a     Show all files specified on the command line. By default, only files that are accessed by at least one process are shown.

       -c     Same as -m option, used for POSIX compatibility.

       -f     Silently ignored, used for POSIX compatibility.

       -k     Kill  processes  accessing the file. Unless changed with -SIGNAL, SIGKILL is sent. An fuser process never kills itself, but may kill
	      other fuser processes. The effective user ID of the process executing fuser is set to its real user ID before attempting to kill.

       -i     Ask the user for confirmation before killing a process. This option is silently ignored if -k is not present too.

       -w     Kill only processes which have write access. This option is silently ignored if -k is not present too.

       -l     List all known signal names.

       -m     name specifies a file on a mounted file system or a block device that is mounted. All processes accessing files on that file  system
	      are listed.  If a directory file is specified, it is automatically changed to name/. To use any file system that might be mounted on
	      that directory. Please note that due the required device ID comparision all mounted  file  systems  the  stat(2)	system	call  will
	      applied  to  every  file	system	even  on network file system (NFS).  If the NFS server does not respond or the network is down the
	      stat(2) may hang forever.

       -n space
	      Select a different name space. The name spaces file (file names, the default), udp (local UDP ports), and tcp (local TCP ports)  are
	      supported.  For ports, either the port number or the symbolic name can be specified. If there is no ambiguity, the shortcut notation
	      name/Ispace (e.g. 80/tcp ) can be used.

       -s     Silent operation. -u and -v are ignored in this mode.  -a must not be used with -s.

       -SIGNAL
	      Use the specified signal instead of SIGKILL when killing processes. Signals can be specified either by name (e.g. -HUP) or by number
	      (e.g. -1). This option is silently ignored if the -k option is not used.

       -u     Append the user name of the process owner to each PID.

       -v     Verbose  mode.  Processes  are  shown  in  a ps-like style. The fields PID, USER and COMMAND are similar to ps. ACCESS shows how the
	      process accesses the file. If the access is by the kernel (e.g. in the case of a mount point, a swap file, etc.),  kernel  is  shown
	      instead of the PID.

       -V     Display version information.

       -4     Search  only  for  IPv4  sockets. This option must not be used with the -6 option and only has an effect with the tcp and udp names-
	      paces.

       -6     Search only for IPv6 sockets. This option must not be used with the -4 option and only has an effect with the  tcp  and  udp  names-
	      paces.

       -      Reset all options and set the signal back to SIGKILL.

FILES

       /proc	 location of the proc file system

EXAMPLES

       fuser -km /home kills all processes accessing the file system /home in any way.

       if fuser -s /dev/ttyS1; then :; else something; fi invokes something if no other process is using /dev/ttyS1.

       fuser telnet/tcp shows all processes at the (local) TELNET port.

RESTRICTIONS

       Processes accessing the same file or file system several times in the same way are only shown once.

       If the same object is specified several times on the command line, some of those entries may be ignored.

       fuser  may  only be able to gather partial information unless run with privileges. As a consequence, files opened by processes belonging to
       other users may not be listed and executables may be classified as mapped only.

       Installing fuser SUID root will avoid problems associated with partial information, but may be undesirable for security	and  privacy  rea-
       sons.

       udp and tcp name spaces, and UNIX domain sockets can't be searched with kernels older than 1.3.78.

       udp and tcp currently  work with IPv6 and IPv4, but the address fields can only be IPv4 addresses.

       Accesses by the kernel are only shown with the -v option.

       The -k option only works on processes. If the user is the kernel, fuser will print an advice, but take no action beyond that.

BUGS

       fuser  -m  /dev/sgX  will  show (or kill with the -k flag) all processes, even if you don't have that device configured. There may be other
       devices it does this for too.

       fuser -m name may hang forever if there are NFS file systems mounted and one of the NFS servers do not respond or the corresponding network
       is down.

       fuser  cannot  report on any processes that it doesn't have permission to look at the file descriptor table for.  The most common time this
       problem occurs is when looking for TCP or UDP sockets when running fuser as a non-root user. In this case fuser will report no access

AUTHORS

       Werner Almesberger <werner@almesberger.net>

       Craig Small <csmall@small.dropbear.id.au>

SEE ALSO

       kill(1), killall(1), lsof(8), pkill(1), ps(1), kill(2).

Linux								    2009-04-26								  FUSER(1)