Versions Compared

Old Version 4

changes.mady.by.user Vitaly Shaburov

Saved on

compared with

New Version Current

changes.mady.by.user Vitaly Shaburov

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

By default, all services for which the value of the general/enabled property is true are started at system boot. To change the milestone to which to boot a system, use one of the following methods. The value of milestone can be the FMRI of a milestone service or a keyword as shown in Table A–2.

  • When booting a SPARC system, specify the -m option to the boot command at the ok prompt. See the -m option in the kernel (1M) man page.

    Code Block
    ok boot -m milestone=milestone

  • When booting an x86 system, edit the GRUB menu to specify the -m option. See Adding Kernel Arguments by Editing the GRUB Menu at Boot Time in Booting and Shutting Down Oracle Solaris 11.2 Systems and the -m option in the kernel (1M) man page.

  • Prior to rebooting a system, use the svcadm milestone command with the -d option. Note that with or without the -d option, this command restricts and restores running services immediately. With the -d option, the command also makes the specified milestone the default boot milestone. This new default is persistent across reboots.

    Code Block
    $ svcadm milestone -d milestone

    This command does not change the current run level of the system. To change the current run level of the system, use the init command.

    If you specify the -s option, svcadm changes the milestone and then waits for the transition to the specified milestone to complete before returning. The svcadm command returns when all instances have transitioned to the state necessary to reach the specified milestone or when it determines that administrator intervention is required to make a transition. Use the -T option with the -s option to specify an upper bound in seconds to complete the milestone change operation or return.

The following table describes SMF boot milestones, including any corresponding Oracle Solaris run level. A system’s run level defines what services and resources are available to users. A system can be in only one run level at a time. For information about run levels,see How Run Levels Work in Booting and Shutting Down Oracle Solaris 11.2 Systems , the inittab (4) man page, and the /etc/init.d/README file. For more information about SMF boot milestones, see the milestone subcommand in the svcadm (1M) man page.

Anchor
Table-A-2
Table-A-2
Table A-2  SMF Boot Milestones and Corresponding Run Levels

SMF Milestone FMRI or Keyword

Corresponding Run Level

Description

none

The none keyword represents a milestone where no services are running except for the master restarter. When none is specified, all services except for svc:/system/svc/restarter:default are temporarily disabled.

The none milestone can be useful when for debugging startup problems. See How to Investigate Problems Starting Services at System Boot for specific instructions.

all

The all keyword represents a milestone that depends on every service. When all is specified, temporary enable and disable requests are ignored for all services. This is the default milestone used by svc.startd.

svc:/milestone/single-user

s or S

Ignore temporary enable and disable requests for svc:/milestone/single-user:default and all services on which it depends either directly or indirectly. Temporarily disable all other services.

svc:/milestone/multi-user

2

Ignore temporary enable and disable requests for svc:/milestone/multi-user:default and all services on which it depends either directly or indirectly. Temporarily disable all other services.

svc:/milestone/multi-user-server

3

Ignore temporary enable and disable requests for svc:/milestone/multi-user-server:default and all services on which it depends either directly or indirectly. Temporarily disable all other services

...

  1. Boot without starting any services.

    The following command instructs the svc.startd daemon to temporarily disable all services and start sulogin on the console.

    Code Block
    ok boot -m milestone=none

    See Specifying the SMF Milestone to Which to Boot for a list of SMF milestones that you can use with the boot -m command.

  2. Log in to the system as root.

  3. Enable all services.

    Code Block
    # svcadm milestone all

  4. Determine where the boot process is hanging.

    When the boot process hangs, determine which services are not running by running svcs -a. Look for error messages in the log files in /var/svc/log.

  5. After fixing the problems, verify that all services have started.

    1. Verify that all needed services are online.

      Code Block
      # svcs -x

    2. Verify that the console-login service dependencies are satisfied.

      This command verifies that the login process on the console will run.

      Code Block
      # svcs -l system/console-login:default

  6. Continue the normal booting process.

...