HP-UX DCE Version 1.9 Release Notes

Chapter 1

About This Document

Known Problems and Work Arounds

This chapter describes the known problems, workarounds, and changes in HP-UX DCE Version 1.9 on HP-UX

11i v2.

Known Problems for HP-UX DCE Version 1.9

This chapter contains a list of the known problems for HP-UX DCE 1.9. Planning and Conﬁguring HP-UX

DCE 1.9 (B3190-90076) also contains additional information about many of these problems.

There are several known problems with integrated login that are documented only in Planning and

Conﬁguring HP-UX DCE 1.9 (B3190-90076). For information about these problems, refer to Chapter 6 of that

manual under "Notes, Cautions, and Warnings" and "Integrating DCE with HP-UX Integrated Login". See

also "Notes, Cautions and Warnings About Using HP-UX Integrated Login with DCE" and "Conﬁguring ux as

a Fallback Technology for DCE."

HP-UX DCE 1.9 Limitations and Known Problems

The limitations of HP-UX DCE 1.9 are as follows:

• In order to reconﬁgure a CDS server, you must follow these steps:

1. Stop and restart the CDS server containing the master replica of the root directory.

2. Stop and restart any other CDS servers containing master replicas for directories that will be

replicated on the newly (re-)conﬁgured server.

These steps are necessary because unconﬁguring and reconﬁguring causes the CDS server principal for

that host to be deleted and then recreated. As a result, cached security contexts in the CDS servers for

master replicas contain out of date information, leading to RPC failures that can cause the cell's

namespace to become unavailable.

As a precautionary measure, HP recommends that all CDS servers containing master replicas be stopped

and restarted any time a CDS server is unconﬁgured from the cell.

• In a split server conﬁguration, if the secd/dtsd server is started before the cdsd/dtsd server, dtsd will

fail to start if CDS services are not available. The problem lies in the dtsd initialization code attempting

to export its time service interface into the namespace.

If this problem occurs, verify that cdsd is running and start dtsd using one of the following commands:

/opt/dcelocal/bin/dtsd -s (for servers)

/opt/dcelocal/bin/dtsd -c (for clients)

• If you use standard UNIX remote login utilities (remsh, rlogin, telnet) to perform remote DCE cell

administration, these utilities may expose the cell administrator's password to network attackers.

The most secure way to perform cell administration is to log in locally on each system that requires

administration.

• A user's DCE credentials are not automatically removed by exiting a shell or logging out.

Use kdestroy to remove credentials that are no longer needed. The -e option of kdestroy removes

credentials older than a speciﬁed number of hours.

• When you run dcecp in "local" mode (that is, when you start dcecp with the local option) on a host with

dced in partial-service mode, there is a possibility that a dcecp "acl modify -add" command will not

work. The interactive dcecp session may hang or a Bus Error may be returned.