The following options are used to provide additional
configuration and to specify servers to be managed:
-c configfile
This option specifies a global configuration file in
addition to the default global configuration file
described below. This file will be processed after the
default global configuration file. If the -c option is
specified more than once, the last configuration file
specified will be used.
-a architecture
This option specifies the target architecture of the
server and is analogous to the -a option of stap. See the
stap(1) manual page for more details. The default
architecture is the architecture of the host.
-r kernel-release
This option specifies a target kernel release of the
server and is analogous to the -r option of stap. See the
stap(1) manual page for more details. The default release
is that of the currently running kernel. A server can
handle multiple releases by specifying multiple -r flags.
-I path
This option specifies an additional path to be searched by
the server(s) for tapsets and is analogous to the -I
option of stap. See the stap(1) manual page for more
details.
-R path
This option specifies the location of the systemtap
runtime to be used by the server(s) and is analogous to
the -R option of stap. See the stap(1) manual page for
more details.
-B options
This option specifies options to be passed to make when
building systemtap modules and is analogous to the -B
option of stap. See the stap(1) manual page for more
details.
-i This option is a shortcut which specifies a server that
handles every release installed in /lib/modules/.
-n nickname
This option allows the specification of a server
configuration by nickname. When -n is specified, a
currently running server with the given nickname will be
searched for. If no currently running server with the
given nickname is found, a server configuration with the
given nickname will be searched for in the configuration
files for default servers, or the path configured in the
global configuration file or the configuration file
specified by the -c option. If a server configuration for
the given nickname is found, the -a, -r, -I, -R, -B and -u
options for that server will be used as if they were
specified on the command line. If no configuration with
the given nickname is found, and the action is start (or
an action behaving like start (see ARGUMENTS), the server
will be started with the given nickname. If no
configuration with the given nickname is found, and the
action is not start (or an action behaving like start), it
is an error. If a nickname is not specified for a server
which is being started, its nickname will be its process
id.
-p pid This option allows the specification of a server
configuration by process id. When -p is specified, a
currently running server with the given process id will be
searched for. If no such server is found, it is an error.
If a server with the given process id is found, the -a,
-r, -I, -R, -B and -u options for that server will be used
as if they were specified on the command line.
-u user-name
Each systemtap compile server is normally run by the user
name stap-server (for the initscript) or as the user
invoking stap-server, unless otherwise configured (see
FILES). This option specifies the user name used to run
the server(s). The user name specified must be a member of
the group stap-server.
--log logfile
This option allows the specification of a separate log
file for each server. Each --log option is added to a
list which will be applied, in turn, to each server
specified. If more servers are specified than --log
options, the default log file (see FILES) will be used for
subsequent servers.
--port port-number
This option allows the specification of a specific network
port for each server. Each --port option is added to a
list which will be applied, in turn, to each server
specified. If more servers are specified than --port
options, a randomly selected port is used for subsequent
servers.
--ssl certificate-db-path
This option allows the specification of a separate NSS
certificate database for each server. Each --ssl option is
added to a list which will be applied, in turn, to each
server specified. If more servers are specified than --ssl
options, the default certificate database (see FILES) for
subsequent servers.
--max-threads threads
This option allows the specification of the maximum number
of worker threads to handle concurrent requests. If
threads == 0, each request will be handled on the main
thread, serially. The default is the number of available
processor cores.
--max-request-size size
This options allows the specification of the maximum size
of an uncompressed client request. The arguement size is
specified in bytes. The default is the 50000 bytes.
--max-compressed-request size
This options allows the specification of the maximum size
of a compressed client request. The arguement size is
specified in bytes. The default is the 5000 bytes.
