Open System Services Management and Operations Guide (G06.25+, H06.03+)

Falling Back to a Previous Release Version Update
Open System Services Management and Operations Guide—527191-002
D-3
Recreating the ZPCONFIG File
== Storage-Pool File The Guardian file identifier of a storage-pool file
== for the fileset. The file must be in the
== $SYSTEM.ZXOSSMON subvolume.
==
== HP recommends that storage-pool file
== identifiers start with ZP.
==
== *Catalog Volume The disk volume where the OSS name server keeps
== the catalog files for the fileset.
==
== HP strongly suggests that you DO NOT use the
== $SYSTEM disk for a catalog volume.
==
== Mount Point The pathname of the directory on which the
== fileset will be mounted. The specified directory
== must already exist.
==
== The name is case-sensitive and must start with /.
== The root fileset mount-point directory must be /.
==
== R/W Flag The R/W flag, which controls read and write
== access to the fileset when the fileset is next
== mounted.
==
== RW allows read and write access
== R allows read-only access
==
== OSS Name Server Name The process name of OSS name server. This name
== MUST be $ZPNS.
==
== OSS Name Server CPUs Primary and backup processor numbers for the OSS
== name server. The OSS name server will be
== restarted on the primary processor if it is
== available, otherwise on the backup processor.
==
== You must supply processor numbers for each fileset,
== but all processor numbers are ignored except for
== those for the root fileset.
==
== HP recommends that you specify processors not
== used by the OSS Monitor or by FSCK (as specified by
== the PARAM OSS^FSCK^CPU).
==
== The primary processor number specified here for
== $ZPNS is ignored if the PARAM OSS^NAMESERVER^CPU
== is used.
==
Figure D-1. Sample ZPCONFIG File (page 2 of 3)