Would booting with kmdb when enable_debug=enable be worthy of inclusion  here ?

Sean.
.
jan damborsky stated:
> If you don't use Automated Installer, you can safely ignore
> this message.
>
> Fix for bug 4443 introduced support for remote ssh access and
> possibility to run Automated Installer (AI) in debug mode.
>
> Following new options are now recognized by AI:
>
> livessh - if set to 'enable', remote ssh access is available
>
> install_debug - if set to 'enable', Automated Installer runs
> in debug mode - see [*] for more details
>
> These options can be specified along with other options in
> installer config file, which is GRUB menu.lst for x86 or
> install.conf file for Sparc.
>
> Those configuration files are populated when install service
> or client are created by 'installadm create-service' or
> 'installadm create-client' commands.
>
> x86
> ---
> menu.lst configuration file is created in /tftpboot/ directory
> with following suffixes:
>
> menu.lst.<service_name> (after 'installadm create-service -n  
> <service_name> ...') or
> menu.lst.01<mac> (after 'installadm create-client -e <mac> ...')
>
> Options are provided as kernel parameters, e.g
>
> kernel$ ... -B install_media=...,livessh=enable,install_debug=enable
>
> sparc
> -----
> install.conf file is populated in <ai_image_dest> directory
> when install service is created - e.g.
> 'installadm create-service -n <service_name> -s <ai_iso_image>  
> <ai_image_dest>'
>
> Options are defined as name-value pairs, e.g
>
> $ cat <ai_image_dest>/install.conf
> ...
> liveshh=enable
> install_debug=enable
>
>
>
> [*] Automated Installer debug mode
> ----------------------------------
> * liblogsvc logging service runs in most verbose debug mode -
>  this affects following modules
>  - Target Discovery
>  - Target Instantiation
>  - Orchestrator
>  - Transfer Module
>  - ICT
>
> * beadm(1M) CLI utility are run with BE_PRINT_ERR=true
>
> * 'pkg install' and 'pkg uninstall' CLI commands are run in
>   verbose mode (with -v option provided) - please see pkg(1)
>   for more details
>
> * messages are captured in following files:
>  /tmp/install_log
>  /var/svc/log/application-auto-installer:default.log
>
>  They are available in /var/sadm/system/logs directory
>  on installed system.
>
>

 Would booting with kmdb when enable_debug=enable be worthy of inclusion  here ?

--
Sean.
.

Reply via email to