Starting HPDPS Components

To start HPDPS within either the Basic Environment or the DCE Extended Environment, use SAM, or do the following:

Start the HPDPS client daemon:

pdstartclient

NOTE: To start HPDPS spooler and supervisor components remotely, you can use SAM, but only after you have started the HPDPS client daemon after logging on to the remote system using the HP-UX rlogin command. You cannot use SAM to remotely start the client daemon.

Use the above command if all users and administrators accessing HPDPS are using the same language. To start an additional HPDPS client daemon on a system that needs to support more than one language, use the pdstartclient command with the -p and -l flags to specify the port and language. For example, to start an additional client daemon on port 1421 using the German locale De_DE, enter:

pdstartclient -p 1421 -l De_DE.iso88591

Start a new supervisor:
pdstartsuv SupervisorName
where SupervisorName is the name of the supervisor that you want to start. For additional information, see “Creating or Starting the Supervisor ” in Chapter 5.
Start a spooler:
pdstartspl SpoolerName
where SpoolerName is the name of the spooler that you want to start. For additional information, see “Creating or Starting the Spooler ” in Chapter 6.

As an alternative, you can use the startup procedures described in “Automatically Starting HPDPS ” shortly.

Viewing Log Files

Standard output and standard error of each HPDPS component started up by the system startup process are redirected to the file:

/var/opt/pd/Component/startup.log

where Component is the spooler or supervisor name, or pdclientd for the client daemon. These log files, in addition to /var/opt/pd/Component/error.log, can be examined for diagnostics on why a component failed to start up.

Starting HPDPS Components

Technical documentation

» Table of Contents

» Index

Viewing Log Files