NAME

dce_config - Configures and starts up DCE

SYNOPSIS

dce_config [-i] [-e environment_file] [-c command_file]

OPTIONS

-iThe -i option tells dce_config to look in the /etc directory of the install area (which is generally /opt/dce1.0/etc) for the component scripts it needs to run.  After you have invoked dce_config once with the -i option, you do not need to use the option again. 

-eThe -e option causes dce_config to source environment_file at startup. environment_file is a user-created file that sets the DCE and DFS variables that specify responses to the dce_config user prompts.  Note that if you do not specify the -e option, dce_config looks for the /etc/dce_config.conf file and sources it if it exists. If the file does not exist, it uses shell variable settings if they are set. 

-cThe -c option causes dce_config to source command_file at startup. command_file is a user-created shell script that initiates configuration processing. 

DESCRIPTION

The dce_config shell command invokes a menu-driven interface that configures and starts up DCE.  The dce_config command displays a hierarchy of menus and invokes individual configuration routines according to users’ menu selections.  The configuration menu consists of initial cell configuration, additional server configuration, and DCE client configuration.  The security server and the first CDS server constitute initial cell configuration.  If you use specify an environment file with the -e option and a command file with the -c option, you can completely automate dce_config processing. 

The Command File

The command file consists of config command lines that specify the component to configure and, for DFS, the type of server.  A sample command file, config.cmd, is provided by with the DCE source. You can copy the file and use it as supplied or you can use it as guide to creating your own environment file.  The sample file is not copied to the install tree during DCE installation.  The config lines are in the form:

config component
            {
             client |
             gda |
             sec {client | server | replica} |
             cds {client | server | replica} |
             dts {clerk | local | global | ntp-provider | null-provider}
             dfs {client | scm | privatefs | fs | fldb}
             }

Where

componentIs one of the following values:

•client—DCE client configuration

•gda—GDA configuration

•sec—Security configuration of any one of the following:

—client—Security client machine

—server—Security master server machine

—replica—Security replica machine

•cds—CDS configuration of any one of the following:

—client—CDS client machine

—server—CDS initial server machine

—replica—Additional CDS server machines

•dts—DTS configuration of any one of the following:

—clerk— DTS clerk machine

—local—DTS local server machine

—global—DTS global server machine

—ntp-provider—DTS NTP time provider machine

—null-provider—DTS null time provider

•dfs—DFS configuration of any one of the following:

—client—DFS client specify

—scm—System Control machine

—privatefs—Private File Server machine

—fs—File Server machine

—fldb—File Location Database Server machine

The Environment File

The Environment file sets the DCE and DFS variables.  The file entries are in the form:

variable=value

To change a value, simply replace it with the new value.  A sample environment file, config.env, is provided with the DCE source. You can copy the file and use it as supplied or you can use it as guide to creating your own environment file.  The sample file is not copied to the install tree during DCE installation. 

The DCE and DFS Variables

The table titled "dce_config Environment Variables" lists the DCE variables you can set for dce_config processing.  The table titled "dfs_config Environment Variables" lists the DFS variables you can set.  In the tables, the term default refers to the original setting assigned to the variable. 

Table 0−0.   dce_config Environment Variables

Table 0−0.   dfs_config Environment Variables

Component Scripts

The dce_config script calls component scripts that reside in the /opt/dcelocal/etc directory (or in the etc directory of the install area) with symbolic links to /etc.  In a custom configuration script, you can call the component scripts directly and supply the required input via the environment variables.  The names and functions of the component scripts follows:

•dce_shutdown—Shuts down all DCE server processes (auditd, dtsd, cdsadv, cdsd, and secd), except for DFS processes (dfsd) via the dcecp or other control programs.  This script must be run on the machine running the daemon processes.  You must be root or another privileged user to run the script.  You should always run the script before reconfiguring DCE. 

If the dce_shutdown script cannot shut down a daemon gently, it sends a kill signal to all the DCE daemons.  If for any reason you do not want to use a control program, you can execute the script manually.  The dce_shutdown script run with its -f option will find and kill the DCE daemons.  This behavior is the same as that of the dce.clean script, which was included in DCE R1.0.3 and previous releases.  DCE R1.1 does not include the dce.clean script, but provides the name as a symbolic link to the dce_shutdown script for the user’s convenience. 

•dfs.clean—Kills DFS server processes.  This script must be run on the machine running the processes.  It should be run before reconfiguring DCE.  (Note that some DFS daemon processes cannot be killed by dfs.clean.) 

•dce.rm [install]—Removes all data and configuration files created by DCE servers after initial configuration except for data and files created by DFS servers. This script must be run on the machine running the processes.  It should be run before reconfiguring DCE.  If you invoke the script with the install parameter, the script removes the binary files added during installation. 

•dfs.rm [install]—Removes data and configuration files created by DFS servers after initial configuration. This script must be run on the machine running the processes, and dced must be running on that machine.  The dfs.rm script should be run before reconfiguring DCE.  If you invoke the script with the install parameter, the script removes the binary files added during installation.  Note that this script invokes the dce.clean script. 

•dce.unconfig hostname—Removes all DCE clients on hostname from the Security and Directory service databases.  It should be run before reconfiguring a client machine. 

•dfs.unconfig hostname—Removes the DFS client on hostname from the Security and Directory service databases.  It should be run before reconfiguring a client machine. 

•dce_com_env—Sets environment variables. 

•dce_config_env—Calls the dce_com_env script that sets the environment variables. 

•dce_com_utils—Contains common functions used by dce_config and dfs_config. 

•dce_config_utils—Contains internal routines used by dce_config scripts. 

•dfs_config—Configures a machine as a DFS server or client. 

•rc.dce—Starts DCE daemons.  This script cannot be run remotely; it must be run on the machine on which the daemons are being started. 

•rc.dfs—Starts DCE daemons.  This script cannot be run remotely; it must be run on the machine on which the daemons are being started. 

Privilege Required

You must have root authority to run the dce_config command. 

EXIT VALUES

In case of an error, this command repeats requests for correct input.  The user can exit the program from any menu. 

RELATED INFORMATION

Books: OSF DCE Administration Guide

Hewlett-Packard Company  —  OSF DCE 1.1/HP DCE 1.5