*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->Tru64 Unix man pages -> dn_setup (8)              
Title
Content
Arch
Section
 

dn_setup(8)

Contents


NAME    [Toc]    [Back]

       dn_setup  -  Creates  and maintains device name databases.
       (The -sanity_check  option is provided for system administration.)

SYNOPSIS    [Toc]    [Back]

       /sbin/dn_setup [option]

OPTIONS    [Toc]    [Back]

       Verifies  the  consistency and currency of the device special
 files and the directory hierarchy. The message Passed
       is displayed if the check is successful.

              The  -sanity_check option is the only option that a
              system administrator should use. Use the  following
              options  only under guidance of your technical support
 representative.  Runs at boot time  to  create
              all  the  default  device special databases, files,
              and directories.  Creates the required device  special
 directories only.  Creates the class and category
 databases only.

       The following options are for internal use  only  and  are
       used  for  debugging.  Using these options can cause unrecoverable
 errors and prevent  your  system  from  booting:
       Deletes  everything  in  the device special directory tree
       and re-creates the entire tree (including  device  special
       files).  Removes all the default device special databases,
       files, and directories. The -init prompts you to  run  the
       following  command, which recreates all the device special
       files.

              # /sbin/dsfmgr -K

DESCRIPTION    [Toc]    [Back]

       The /sbin/dn_setup script  runs  automatically  at  system
       startup  to  create  device  special file names and is not
       normally used by administrators.  However, you  might  see
       device-related error messages at the system console during
       system startup, indicating that the system  is  unable  to
       assign  device  special file names. Following such errors,
       use the -sanity_check option to  verify  the  device  name
       database.

       If  the  -sanity_check option displays messages other than
       Passed, use the dsfmgr command  to  further  diagnose  and
       correct the problem.

       The  /sbin/bcheckrc  utility  also verifies device special
       files during system startup. If  /sbin/bcheckrc  discovers
       any  problems,  it  displays  the following message at the
       console: bcheckrc: Device Naming failed initial check.
           Run dsfmgr -v, and if no errors are
           reported, exit or type CTRL-D to continue
           booting normally.






RESTRICTIONS    [Toc]    [Back]

       Other than the -sanity_check option, use the dn_setup command
  only  under  the  guidance of your technical support
       representative. Otherwise, you might alter critical system
       databases  and  prevent  the  system  from  booting.  Such
       database problems might not be  recoverable,  requiring  a
       full restoration of the operating system from your backup.

EXAMPLES    [Toc]    [Back]

       Typical use of the command is as follows: # /sbin/dn_setup
       -sanity_check Passed.

SEE ALSO    [Toc]    [Back]

      
      
       Commands: dsfmgr(8), bcheckrc(8)

       Hardware Management



                                                      dn_setup(8)
[ Back ]
 Similar pages
Name OS Title
scsimgr Tru64 manage SCSI devices and device databases
dsfmgr Tru64 Manages device special files in the /dev directory and their associated databases
kmknod Tru64 Creates device special files for static kernel layered products
createlabel Tru64 creates a disk label structure for a disk device
EvmConnWait Tru64 Maintains connection with the EVM daemon
EvmConnDispatch Tru64 Maintains connection with the EVM daemon
EvmConnCheck Tru64 Maintains connection with the EVM daemon
EvmConnFlush Tru64 Maintains connection with the EVM daemon
make Tru64 Maintains program dependencies
sysconfig Tru64 Maintains the kernel subsystem configuration
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service