---

   stap-server    ( 8 )

---

Individual Server Configuration

Each server configuration file configures a server to be started when no server is specified for the start action, or an action behaving like the start action (see ARGUMENTS). Each configuration file contains variable assignments used to configure an individual server.

Each line beginning with a '#' character is ignored. All other lines must be of the form VARIABLE=VALUE. This is not a shell script. The entire contents of the line after the = will be assigned as-is to the variable.

Each configuration file must have a filename suffix of .conf. See stappaths(7) for the default location of these files. This default location can be overridden in the global configuration file using the -c option (see OPTIONS).

The following variables may be assigned:

ARCH Specifies the target architecture for this server and corresponds to the -a option (see OPTIONS). If ARCH is not set, the architecture of the host will be used.

RELEASE Specifies a kernel release for this server and corresponds to the -r option (see OPTIONS). If RELEASE is not set, the release of the kernel running on the host will be used.

BUILD Specifies options to be passed to the make process used by systemtap to build kernel modules. This an array variable with each element corresponding to a -B option (see OPTIONS). Using the form BUILD=STRING clears the array and sets the first element to STRING. Using the form BUILD+=STRING adds STRING as an additional element to the array.

INCLUDE Specifies a list of directories to be searched by the server for tapsets. This is an array variable with each element corresponding to a -I option (see OPTIONS). Using the form INCLUDE=PATH clears the array and sets the first element to PATH. Using the form INCLUDE+=PATH adds PATH as an additional element to the array.

RUNTIME Specifies the directory which contains the systemtap runtime code to be used by this server and corresponds to the -R option (see OPTIONS).

USER Specifies the user name to be used to run this server and corresponds to the -u option (see OPTIONS).

NICKNAME Specifies the nickname to be used to refer to this server and corresponds to the -n option (see OPTIONS).

LOG Specifies the location of the log file to be used by this server and corresponds to the --log option (see OPTIONS).

PORT Specifies the network port to be used by this server and corresponds to the --port option (see OPTIONS).

SSL Specifies the location of the NSS certificate database to be used by this server and corresponds to the --ssl option (see OPTIONS).

MAXTHREADS Specifies the maximum number of worker threads to handle concurrent requests to be used by this server and corresponds to the --max-threads option (see OPTIONS).

MAXREQSIZE Specifies the maximum size of an uncompressed client request, to be used by this server and correspnds to the --max-request-size option (see OPTIONS).

MAXCOMPRESSEDREQ Specifies the maximum size of an compressed client request, to be used by this server and correspnds to the --max-compressed-request option (see OPTIONS).

Here is an example of a server configuration file:

ARCH= USER= RELEASE= NICKNAME=native

By keeping the ARCH, USER, and RELEASE fields blank, they will default to the current arch and release and use the default user.

A more specific example:

ARCH=i386 RELEASE=2.6.18-128.el5 PORT=5001 LOG=/path/to/log/file

And here is a more complicated example:

USER=serveruser RELEASE=/kernels/2.6.18-92.1.18.el5/build INCLUDE=/mytapsets INCLUDE+=/yourtapsets BUILD='VARIABLE1=VALUE1 VARIABLE2=VALUE2' DEFINE=STP_MAXMEMORY=1024 DEFINE+=DEBUG_TRANS RUNTIME=/myruntime NICKNAME=my-server SSL=/path/to/NSS/certificate/database