HP Serviceguard Quorum Server Version A.03.00 Release Notes, December 2007

HP Serviceguard Quorum Server Version A.03.00 Release Notes
Configuring and Running the Quorum Server
Chapter 1 25
7. Update the authorization file if necessary.
See “Creating and Updating the Authorization File” on page 26.
8. Run the cluster and start the quorum server package.
Running the Quorum Server on a Single System
Specifying a Log File
By default, Quorum Server run-time messages go to stdout and stderr.
HP recommends that you create a directory such as /var/adm/qs, then
redirect stdout and stderr to a file in this directory (for example,
/var/adm/qs/qs.log) when you start the Quorum Server; see the
sample /etc/inittab entries in the examples below. Recommended
pathnames are in Table 1-2 on page 24.
Running the Quorum Server
NOTE If you have just installed the quorum server, or if you are adding new
cluster nodes, or implementing the alternate-subnet functionality (for a
cluster running a version of Serviceguard that supports it; see
“Compatibility with Serviceguard Versions” on page 12) you must update
the authorization file; see “Creating and Updating the Authorization
File” on page 26.
You must have root capability to run the Quorum Server. On a single
system, configure the Quorum Server to start up when the system on
which it is installed restarts or reboots. Create an entry such as the
following in the /etc/inittab file:
• For HP-UX:
qs:345:respawn:/usr/lbin/qs >> /var/adm/qs/qs.log 2>&1
• For Red Hat Linux (all in one line):
qs:345:respawn:/usr/local/qs/bin/qs >> /var/log/qs/qs.log
2>&1
• For SUSE Linux:
qs:345:respawn:/opt/qs/bin/qs >> /var/log/qs/qs.log 2>&1