Chapter 7 HPSS User Interface Configuration
HPSS Installation Guide September 2002 451
Release 4.5, Revision 2
are run on one machine, but leads to the possibility that an aggregate will be overlooked and not
kept properly synchronized.
On the other hand, if "permissiveMount" is not specified, HDM will abort mount events for
aggregates it does not manage. While this is safer, it cannot be used on a machine where multiple
copies of HDM are running.
The "permissiveMount" flag must be specified if several HDM servers are to be run on one
machine, and should never be specified when only one is to be run.
If the "stdout" keyword is present on the Flags line, HDM will write all messages to standard
output. While this option can help with debugging, its use is generally discouraged.
HPSSDMAPHostNamespecifies the host name for the machine where the HDM will be run. This
should be a fully qualified host name. For example,tardis.ca.sandia.gov. Be sure to use the host
name where HDM will be run, not the host name where the DMAP Gateway will be run.
HPSSDMAPTCPPortspecifies the TCP port used by the HDM to listen for requests from the
DMAPGateway. Conventionally,this will be 6002. Check /etc/services to ensure that this port is not
alreadybeing used by another program. Do not confuse this port number with the port used by the
DMAP Gateway to receive requests from HDM, whose value is conventionally 7001. Make sure
both port numbers mentioned here are consistent between HDM and DMAP Gateway
configurations.
When multiple HDM servers are configured, each HDM must have a unique TCP port.
LogRecordMaskspecifies the type of messages recorded in the message log. A series of keywords,
separated by white space, define the messages that are to be recorded. For example:
LogRecordMask alarm event trace debug
Legal keywords and their meanings are:
Table 7-4 LogRecordMask Keywords
Keyword Description
accounting accounting information; not currently used
alarm errorconditions of interest to the administrator
debug low level error message for troubleshooting
event informational messages (e. g., system starting)
request request-specific messages; not currently used
security security related events; not currently used
status status messages; not currently used
trace program flow and other low level messages