FSTAT(1)                    386BSD Reference Manual                   FSTAT(1)

NAME
     fstat - file status

SYNOPSIS
     fstat [-fnv] [-M core] [-N system] [-u user] [filename...]

DESCRIPTION
     Fstat identifies open files.  A file is considered open by a process if
     it was explicitly opened, is the working directory, root directory,
     active pure text, or kernel trace file for that process.  If no options
     are specified, fstat reports on all open files in the system.

     Options:

     -f      If additional filename arguments are present, restrict
             examination to files open in the same filesystem as the named
             file arguments.  For example, to find all files open in the
             filesystem where the directory /usr/src resides, type ``fstat -f
             /usr/src''.

     -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 /vmunix.

     -n      Numerical format.  Print the device number (maj,min) of the
             filesystem the file resides in rather than the mount point name.
             Also, print the mode of the file in octal instead of symbolic
             form.

     -p      Report all files open by the specified process.

     -u      Report all files open by the specified user.

     -v      Verbose mode.  Print error messages upon failures to locate
             particular system data structures rather than silently ignoring
             them.  Most of these data structures are dynamically created or
             deleted and it is possible for them to disappear while fstat is
             running.  This is normal and  unavoidable since the rest of the
             system is running while fstat itself is running.

     filename ...
             Restrict reports to the specified files.

     The following fields are printed:

     USER   The username of the owner of the process (effective uid).

     CMD    The command name of the process.

     PID    The process id.

     FD     The file number in the per-process open file table or one of the
            following special names:

                  text - pure text inode wd   - current working directory
                  root - root inode tr   - kernel trace file

            If the file number is followed by an asterisk (``*''), the file is
            not an inode, but rather a socket, FIFO, or there is an error.  In
            this case the remainder of the line doesn't correspond to the
            remaining headers -- the format of the line is described later

            under Sockets.

     MOUNT  If the -n flag wasn't specified, this header is present and is the
            pathname that the filesystem the file resides in is mounted on.

     DEV    If the -n flag is specified, this header is present and is the
            major/minor number of the device that this file resides in.

     INUM   The inode number of the file.

     MODE   The mode of the file.  If the -n flag isn't specified, the mode is
            printed using a symbolic format (see strmode(3));  otherwise, the
            mode is printed as an octal number.

     SZ|DV  If the file is not a character or block special, prints the size
            of the file in bytes.  Otherwise, prints the major/minor device
            number that the special device refers to.

     NAME   The last component of the filename(e.g. omitting the preceeding
            pathname if any).  Since different directory entries may reference
            the same file (via ln(2)),  the name printed may not be the actual
            name that the process originally used to open that file.

SOCKETS
     The formating of open sockets depends on the protocol domain.  In all
     cases the first field is the domain name, the second field is the socket
     type (stream, dgram, etc), and the third is the socket flags field (in
     hex).  The remaining fields are protocol dependent.  For tcp, it is the
     address of the tcpcb, and for udp, the inpcb (socket pcb).  For unix
     domain sockets, its the address of the socket pcb and the address of the
     connected pcb (if connected).  Otherwise the protocol number and address
     of the socket itself are printed.  The attempt is to make enough
     information available to permit further analysis without duplicating
     netstat(1).

     For example, the addresses mentioned above are the addresses which the
     ``netstat -A'' command would print for tcp, udp, and unixdomain.  Note
     that since pipes are implemented using sockets, a pipe appears as a
     connected unix domain stream socket.  A unidirectional unix domain socket
     indicates the direction of flow with an arrow (``<-'' or ``->''), and a
     full duplex socket shows a double arrow (``<->'').

BUGS
     Since fstat takes a snapshot of the system, it is only correct for a very
     short period of time.

SEE ALSO
     netstat(1),  nfsstat(1),  ps(1),  systat(1),  vmstat(1),  iostat(8),
     pstat(8)

HISTORY
     The fstat command appeared in 4.3BSD-Tahoe.

4th Berkeley Distribution        July 22, 1991                               2