Configuration files and shell scripts are installed with
the executable files when you install the Server in a supported UNIX environment. These objects
establish defaults for the Server and must be customized to reflect
your network environment. Use a text editor (for example, vi, emacs,
CDE Text Editor, textedit, or xedit) to modify these files.
Configuration Files
Configuration
files are ASCII text files and are installed in the /etc directory
that is subordinate to the PSTHOME directory. PSTHOME is an environment
variable, set during installation, that points to the directory in
which the Server is installed.
The configuration
file names for the Server are:
- pstserv.cfg
- Configures prosvce, the Server daemon.
- pstlocal.cfg
- Configures local command line.
The appropriate Configuration file
is loaded and validated when pr0svce or the Command Line Utility starts
up. You can also use pr0svce -v to validate pstserv.cfg
or pr0cmnd -v to validate pstlocal.cfg.
To reload the configuration file for prosvce while it
is running, use pr0svce -u from a console under the
user account for the daemon (or use pr0svce -u userid from
root). After all clients have logged off, the file is read, reloaded,
and validated. A console message and system log verify the file has
been loaded.
Note: Use pr0svce -L (or use pr0svce
-L userid from the root account) to determine if the
system is waiting to reload.
Shell Scripts
The
installed shell scripts are:
- RTSETENV
- Defines the operating environment for the Server.
Installed in the PSTHOME directory and designed to be included in
a user .profile or .login script to set up the environment for the
Server or command line on login.
- RTSERVER
- Provides commands that allow you to manipulate the
Server process. Installed in /sbin, subordinate to the PSTHOME directory.
- RT4S
- Used to start or stop the Server from init processing.
Installed in /sbin, subordinate to the PSTHOME directory, RT4S should
be executed only as part of the system boot procedure.
Conventions
The
following conventions are used in shell scripts and .cfg files:
- One parameter per line.
- Blank lines and leading and trailing blanks within
a line are ignored.
- Use double quotes or the escape character (\) to
pass a special character to processing:
- Enclose a string that includes ‘# ' in double
quotes (e.g., "text#here").
- To include a double quote (") within a quoted string,
use the escape character, \ (e.g., \").
- Precede a special character that is not in a quoted
string with the ‘escape' character, \ (e.g., \#, \\).
- References to environment variables are in the form
${environmentvariablename}. An environment variable that does
not exist equates to a NULL string (“ ”). For example, AAA${NOT_EXIST}BBB
is treated as AAABBB.
- Parameters and keywords are not case-sensitive.
Directories, file names, User IDs, and passwords are case-sensitive.
- Keywords shown as 0 (zero) in the following text
can also be entered as f, or false, while keywords shown as 1 can
be entered as t, or true.
- Comments are allowed after an entry and must begin
with ‘# '.
Syntax
The syntax
conventions used to describe the configuration files, shell scripts,
and commands are:
- parameter
- Parameters and keywords can be entered in UPPER,
lower, or Mixed case.
- text
- Variable text is shown in lower-case italics.
- ( )
- Delimiter to group a series of qualifiers.
- [ ]
- Delimiter for optional parameters or settings.
- { }
- Delimiter for a choice from which you must select
one.
- < >
- Delimiter for a choice from which you may select
any or none.
- |
- Separates options.