Stopping Historical Server On Unix - Sybase 12.5.1 User Manual

Historical server
Table of Contents

Advertisement

Starting and stopping Historical Server on UNIX platforms

Stopping Historical Server on UNIX

Who can shut down Historical Server
34
Use the same account each time you start Historical Server, if you want the
new instance to have access to previously recorded sessions. See "The
operating system start-up account" on page 10 for more information.
Set the $SYBASE environment variable to the root directory of the Sybase
installation.
The $SYBASE environment variable must contain the name of a directory
that has the appropriate locales and charsets subdirectories for Historical
Server. These subdirectories were created and populated automatically by
the installation procedure.
The $SYBASE environment variable also identifies the default location of
the interfaces file. Use parameters to the
the default location.
Historical Server displays the following message to indicate that start-up was
successful:
Initialization is over. Ready to accept connections.
Historical Server writes messages to its log file during start-up. You can ignore
these messages if start-up was successful. If start-up is not successful, examine
the log file to research the problem.
The default path name for the Historical Server log file is hs.log in the current
directory at the time of start-up. You can override this default path name with
the
parameter (the letter l) to the
-l
This section describes:
Who can shut down Historical Server
Determining current activity on Historical Server
Deferred versus immediate shutdown
Detailed shutdown procedures
If the start-up command specifies a superuser account, then only the superuser
account can stop Historical Server. If a superuser is not specified in the start-
up command, any user can stop Historical Server.
command to override
histserver
command.
histserver
Historical Server

Advertisement

Table of Contents
loading

Table of Contents