netuser(1M)                     TCP/IP R4.11                     netuser(1M)


NAME
       netuser - identify processes using a network endpoint

SYNOPSIS
       netuser [ -kun ] endpoint [[-] [ -kun ] endpoint] ...

       where endpoint is:
       { tcp | udp } localip-localport remoteip-remoteport

       netuser -A [ -kun ]

DESCRIPTION
       netuser lists the process ids of the processes using a network
       endpoint.  The options are as follows:

       -u     The login name, in parentheses, follows the process id.

       -k     The SIGKILL signal is sent to each process.  Only a user with
              appropriate privilege can terminate another user's process
              (see kill(2)).  On a generic DG/UX system, appropriate
              privilege is granted by having an effective UID of 0 (root).
              See the appropriateprivilege(5) man page for more
              information.

       On a system with DG/UX information security, appropriate privilege is
       granted by having one or more specific capabilities enabled in the
       effective capability set of the user.  See the capdefaults(5) man
       page for the default capabilities for this command.  -n Disable the
       translation of port numbers and IP addresses to symbolic names.

       -      Clears previously set options.

       -A     Print the process information for all TCP and UDP endpoints.

       The -u, -k and -n may be respecified between groups of endpoints.
       The options in effect will be the new options and the options
       previously set.  A single dash (-) cancels any -u, -k or -n 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.  Endpoint
       addresses are written to standard error.  For each process id, the
       descriptor type, either "c" for character special or "s" for socket
       is written to standard error.  All diagnostic messages are written to
       standard error.

EXAMPLES
       netuser udp "*-snmp" "*-*"
              This command line will return the process which has bound to
              udp port specified by service snmp but has not bound the local
              IP address nor connected to a peer. Sample output from this
              command line:

              udp <*-snmp><*-*>: 849s

       netuser udp 0.0.0.0-snmp 0.0.0.0-0
              This command line returns the same information as the one
              above.

       netuser -A 2>&1 | grep grumpy
              This Bourne shell command will list all connections with host
              grumpy.  Sample output from this command line:

              tcp <happy-XV11><grumpy-1795>: 850s
              tcp <happy-XV11><grumpy-1793>: 1027s

       netuser -ku tcp happy-1080 99.0.1.30-telnet
              If typed by a user with appropriate privilege, terminates all
              processes that are using the telnet connection between local
              address happy-1080 and the remote telnet server 99.0.1.30.

DIAGNOSTICS
       Exit status is 1 if a system call failure occurred.
              Additional diagnostic messages identify the failed system
              call.

       Exit status is 2 if an invalid option switch is used.
              Invalid option is displayed.

       Exit status is 3 if there is missing address information.

       Exit status is 4 if invalid address information is used.
              Additional diagnostic messages describe the invalid address
              part.

       Exit status is 5 if the specified address was not found.

NOTES
       Some endpoints are created by internal kernel calls and do not show
       up in any process' descriptor table.  In addition, some TCP endpoints
       may be in the TIME_WAIT state.  This indicates that the local process
       has closed the endpoint but the endpoint persists in order to
       retransmit last packets.

LIMITATIONS
       netuser only supports tcp and udp protocols.  Raw endpoints are not
       supported.

       netuser does not properly handle tcp and udp service names that
       contain hyphens; the service port numbers should be used in place of
       the names.

       netuser can fail if insufficient memory is available to load the
       entire TCP or UDP connection table.

SEE ALSO
       ps(1), dgfileinfo(2), dgprocessinfo(2), kill(2), signal(2),
       inetaddr(3), appropriateprivilege(5).


Licensed material--property of copyright holder(s)