NAME | SYNOPSIS | CAUTION | DESCRIPTION | DIAGNOSTICS | EXIT STATUS | SEE ALSO
Do not use this command, use reconfig(1M) instead. Only authorized service providers should use dr_cmd_auto_config, which runs in the DR shell, and only when they cannot use reconfig(1M). Performing this operation may cause device files to be remapped and known devices to be renamed.
As of the Solaris 8 GA release, manual reconfiguration is not needed. A new DDI subsystem, devfsadm, completes all of the reconfiguration tasks.
The system administrator would normally run dr_cmd_auto_config after a new system board has been attached to a running domain to make the devices on the boards available immediately. The automatic configuration of the Solaris operating environment consists of the following commands, in the order shown:
drvconfig(1M), devlinks(1M), disks(1M), and tapes(1M).
This command is available only for DR 2.0 domains (that is, domains that use the DR daemon) on the Sun Enterprise 10000 server. You can use domain_status(1M) to determine the DR version running on the domain.
See DIAGNOSTICS in the reconfig(1M) man page.
If dr_cmd_auto_config succeeds it returns a 0 result code in the dr_return global variable. If it fails, it returns a 1.
Tcl parsing errors prevent DR commands from running which, in turn, leaves dr_return uninitialized. In such cases, the dr_return error code is meaningless. See dr(1M) for more information concerning return codes.
reconfig(1M) in this reference manual
drvconfig(1M), devlinks(1M), disks(1M), dr_daemon(1M), ports(1M), tapes(1M) in man pages section 1M: System Administration Commands
NAME | SYNOPSIS | CAUTION | DESCRIPTION | DIAGNOSTICS | EXIT STATUS | SEE ALSO