Sybase 12.5.1, Руководство пользователя

Страница: 98 / 210

hs_shutdown
84
Historical Server
hs_shutdown no_wait
Usage
• If you use the
hs_shutdown
command without the
no_wait
option and
then want to cancel the request, you can send an interrupt to Historical
Server to cancel the shutdown request. A DB-Library application
calls the
dbcancel()
function and a CT-Library application calls the
ct_cancel()
function to cause such an the interrupt. The
isql
command
generates one of these calls when you send it an interrupt signal,
which usually is done by typing Ctrl+C.
• You can request an immediate shutdown of Historical Server at any
time by sending one of the following four signals:
• SIGQUIT (quit)
• SIGINT (interrupt)
• SIGABORT (abort)
• SIGTERM (terminate)
Reception of one of these signals at any time (including while waiting
for the
hs_shutdown
command to complete) is equivalent to issuing
the
hs_shutdown no_wait
command.
Warning! Sybase strongly recommends that you do not use the kill
signal (SIGKILL) to shut down Historical Server. The kill signal does
not permit any controlled cleanup to be done and may result in data
loss.
• If any active sessions were terminated during the shutdown,
Historical Server writes information about the sessions to its log
file. Active sessions are recording sessions or playback sessions
in the process of creating a new recording session.
• If a superuser was specified in the Historical Server start-up
command, the only user who can shut down Historical Server is
the superuser. If a superuser was not specified, any user can shut
down Historical Server.
• See Chapter 3, “Starting and Stopping Historical Server” for
more information about stopping Historical Server.