Table of Contents

Name

linxstat - display specific information about LINX

Synopsis

linxstat [-a] [-b] [-f] [-h] [-H] [-q] [-s] [-S] [-t type ] [-T] [-l length ] [-n hunt_name ]

Description

linxstat is a utility to display the status of the LINX communication system, including information about all local and known remote LINX endpoints and LINX links to remote nodes. The names, types, status and local identifiers are displayed as well as queues, attaches and hunts. The information is fetched from the LINX kernel module. The following columns can be output, in addition to a leading summary (compare the example):

PID is the id of the process owning the LINX endpoint or LINX link. As each remote endpoint are represented by a local LINX endpoint with a local identifier (spid), they are all owned by one common local process.

spid is the local LINX binary identifier for the LINX endpoint or LINX link.

name is the huntname of the LINX endpoint or LINX link. If a name is too long for the column, a "+" sign is displayed and the tailing part of the name.

type is the type of entry, i.e. local for a local LINX endpoint, link for a LINX link to another node, remote for a local representation of a remote LINX endpoint, zombie for a LINX endpoint which has been closed, illegal if an endpoint structure is illegal. unknown if linxstat cannot reach the LINX endpoint.

state is the state of the endpoint or link. The main states are running not waiting for anything, recv while waiting to receive signal buffers, poll while waiting for events with the poll(2) or select(2) system call, unknown if linxstat cannot get the state.

queue is the receive queue. This is the number of signal buffers delivered to the LINX endpoint, but not yet received.

attach(from/to) are the pending attach information. Both the number of attaches to each LINX endpoint from other endpoints and the number of attaches from each endpoint to other endpoints are displayed.

hunt are pending hunts owned by each LINX endpoint. It also includes pending hunts, sent by others but with this endpoint as sender.

tmo are pending timeouts for each LINX endpoint.

Options

-a
Display more verbose pending attach information.
-b
Batch mode, only display the number of open LINX endpoints.
-f
Print receive filters.
-h
Display a short help message.
-H
Display more verbose pending hunt information.
-q
Display more verbose receive queue information.
-s
Display less information (simple). Only endpoint-specific information are displayed, no summary, no title and no counter columns.
-S
If the LINX kernel module has been compiled with per-socket statistics (SOCK_STAT) then linxstat can display statistics for each socket.
-t type
Display only sockets of the specified type.
-T
Print pending timeouts.
-l length
Specify length of name to be printed, default 18, minimum 5
-n hunt_name
Print info

only for hunt_name

Files

None.

Diagnostics

linxstat writes all information to standard output.

Known Bugs

linxstat queries are not atomic, the state of the system may change while linxstat is running.

Example

This is a displayed list from linxstat.


 local:5 remote:1 link:1
 pending attach:2
 pending hunt:0
 pending timeout:0
 queued signals:0
  PID spid    name               type   state  queue attach(f/t) hunt tmo
24903 0x10003 linx16             link   -      0     1/0         0    0
24903 0x10004 +16/apitest_server remote -      0     0/0         0    0
24909 0x10001 apitest_client     local  run    0     0/1         0    0
24909 0x10024 +est_attach_parent local  poll   0     1/1         0    0
24909 0x10005 not bound          local  run    0     0/0         0    0
24958 0x10023 +test_attach_child local  recv   0     0/0         0    0
24963 0x10025 linxstat           local  run    0     0/0         0    0

With -a, more information is displayed after each line with pending attaches. Extracts from a table, created by linxstat -a:


 local:4 remote:1 link:1
 pending attach:1
 pending hunt:0
 pending timeout:0
 queued signals:0
 PID  spid    name               type  state  queue attach(f/t) hunt tmo
25053 0x10002 linx16             link  -      0     1/0         0    0
        Attach info (from):
          [attref:0x00000400   from:0x00010001 signo:0          size: 0]
25053 0x10003 +16/apitest_server remote  -    0     0/0         0    0
25059 0x10001 apitest_client     local run    0     0/1         0    0
        Attach info (to):
          [attref:0x00000400   to:0x00010001 signo:0          size:   0]
25059 0x10004 not bound          local run    0     0/0         0    0
25059 0x10014 +inx_receive_w_tmo local poll   0     0/0         0    0
25083 0x10015 linxstat           local run    0     0/0         0    0

See Also

linx(7) , linx_attach(3) , linx_hunt(3) , linx_open(3) , linxdisc(8) , linxdisc.conf(5) , linxcfg(1)

Author

Enea LINX team

Copyright

Copyright (c) 2006-2011, Enea Software AB All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of Enea Software AB nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.


Table of Contents