SRM - Documentation

^ SRM Documentation
^ Administration documentation

- Introduction
- Compiling
- Installation
- Configuration settings

Appendix A. Configuration settings

Table of Contents
Global settings
Module settings

This appendix lists all the possible settings for the different portions of SRM.

If an error occurs during parsing, srmd will stop loading and give a parse error on the coresponding line, like so:

parse error at line 10 on }

Global settings

The first section of the configuration file is the module settings. This portion of the configuration file informs the srmd system where to find modules and which modules to load.

modules { path = "/usr/local/srm/lib/"; load "auth"; load "php4"; }

This path directive specifies where the SRM modules can be found on the filesystem.

The load keyword inform SRM to attempt loading the specified module into the daemon. If the module cannot be loaded, a message is displayed to either the screen or the logfile. This keyword is only valid in the module section of the ini file.

The second section of the ini file are srm specific settings. These settings control various aspects of the SRM daemon, like which tcp port to use and where the logfile is located.

srm { port = 7777; sockname = "/tmp/srm.socket"; log_level = 99; log_file = "/var/log/srm"; }

The port directive is the TCP portnumber on which SRM will listen for connections. SRM will also always listen for connections on an AF_UNIX socket.

The socket is configurable with the sockname directive and defaults to /tmp/srm.socket.

The log_level directive controls what types of notices, warnings, and errors will be dumped to the error log. The value for the logging level is a number between 0 and 100. The higher the number, the more message are shown. The default and recommended level is 30. The log_level values are shown here:

Table A-1. Logging levels

Log level	Description
1	Fatal errors, which include files that are required, but could not be openend.
5	Caught signals, like SIGQUIT, or SIGINT.
10	Start up and shut down messages.
20	Security messages and connection errors.
35	Informational messages, which includes showing module info at startup.
40	Connection requests.
45	Locking and protocol messages.
50	Storing and retrieving application level variables.
60	Statistical information.

The log_file directive specifies the location of the logfile within the local file system.

The third section is the store section, which is used to define the size of various internal memory structures for SRM. Typically there is no reason to change these values, as they are optimized for upto 5,000 different application variables.

store { applications_items = 2048; session_items = 4096; application_lock_items = 1024; session_lock_items = 1024; session_save_patch = "/var/state"; }

The session_save_path directive is used to specify where SRM should dump the contents of the application variables when it is shut down. On startup the data is read again, so no data will be lost if SRM needs to be shutdown.

The banana section dictates the various behaviors for banana functionality to exist.

banana { class_path = "/opt/srm/banana"; }

The class_path directive specifies where the Banana class loader tries to find the Banana classes from.

Prev: Starting the SRM daemon at boot time Next: Module settings