[ Previous |
Next |
Contents |
Glossary |
Search ]
Performance Toolbox Version 1.2 and 2 for AIX: Guide and Reference
xmservd Command
The xmservd daemon is
always started from inetd. Therefore, command line options
must be specified on the line defining xmservd to inetd
in the file /etc/inetd.conf.
Syntax
xmservd [-v] [-b
UDP_buffer_size] [-i min_remote_interval] [-l
remove_consumer_timeout] [-m supplier_timeout]
[-p trace_level] [-s max_logfile_size]
[-t keep_alive_limit] [-x xmservd_execution_priority]
Flags
All command line options are
optional. The options are:
- v
- Verbose. Causes parsing information for the xmservd
recording configuration file to be written to the xmservd
log file.
- b
- Defines the size of the buffer used by the daemon to send
and receive UDP packets. The buffer size must be
specified in bytes and can be from 4,096 to 16,384 bytes.
The buffer size determines the maximum number of data
values that can be sent in one data_feed packet.
The default buffer size is 4096 bytes, which allows for
up to 124 data values in one packet.
- i
- Defines the minimum interval in milliseconds that data
feeds can be sent with. Default is 500 milliseconds. A
value between 100 and 5,000 milliseconds can be
specified. Any value specified is rounded to a multiple
of 100 milliseconds. Whichever minimum remote interval is
specified causes all requests for data feeds to be
rounded to a multiple of this value. See further details
in section "Rounding
of Sampling Interval"
.
- l
- (Lowercase L). Sets the time_to_live after feeding
of statistics data has ceased as described in section
"Life and Death
of xmservd"
.
Must be followed by a number of
minutes. A value of 0 (zero) minutes causes the daemon to
stay alive forever. The default time_to_live is 15
minutes.
This value is also used to
control when to remove inactive data-consumers as described in
"Removing Inactive
Data-Consumers" .
- m
- When a dynamic data-supplier is active, this value sets
the number of seconds of inactivity from the DDS before
the SPMI assumes the DDS is dead. When the timeout value
is exceeded, the SiShGoAway flag is set in the
shared memory area and the SPMI disconnects from the
area. If this flag is not given, the timeout period is
set to 90 seconds.
The
size of the timeout period is kept in the SPMI common
shared memory area. The value stored is the maximum value
requested by any data consumer program, including xmservd.
- p
- Sets the trace level, which determines the types of
events written to the log file /etc/perf/xmservd.log1
or /etc/perf/xmservd.log2. Must be followed
by a digit from 0 to 9, with 9 being the most detailed
trace level. Default trace level is 0 (zero), which
disables tracing and logging of events but logs error
messages.
- s
- Specifies the approximate maximum size of the log files.
At least every time_to_live minutes, it is checked
if the currently active log file is bigger than max_logfile_size.
If so, the current log file is closed and logging
continues to the alternate log file, which is first reset
to zero length. The two log files are /etc/perf/xmservd.log1
and /etc/perf/xmservd.log2. Default maximum
file size is 100,000 bytes. You can not make max_logfile_size
smaller than 5,000 or larger than 10,000,000 bytes.
- t
- Sets the keep_alive_limit described in section
"Life and Death
of xmservd"
. Must be followed by a number of
seconds from 60 to 900 (1 to 15 minutes). Default is 300
seconds (5 minutes).
- x
- Sets the execution priority of xmservd. Use this
option if the default execution priority of xmservd
is unsuitable in your environment. Generally, the daemon
should be given as high execution priority as possible (a
smaller number gives a higher execution priority).
On systems other than IBM RS/6000
systems, the -x flag is used to set the nice
priority of xmservd. The nice priority is a value
from -20 to 19. Default is -20.
[ Previous |
Next |
Contents |
Glossary |
Search ]