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) through 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.
The dce_shutdown script attempts to shut down a daemon gently. If it fails to do so, it will send a kill signal to all the DCE daemons.
The dce_shutdown script can also be run directly if for any reason you do not want to use a control program.When the script is run with the -f option, it 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.
|