shutdown(8) 맨 페이지 - 윈디하나의 솔라나라

개요

섹션
맨 페이지 이름
검색(S)

shutdown(8)

System Administration Commands                                     shutdown(8)



NAME
       shutdown - shut down system, change system state

SYNOPSIS
       /usr/sbin/shutdown [-y] [-g grace-period] [-r | -p | -i init-state]
            [message]

DESCRIPTION
       shutdown  is executed by a system administrator to change the run level
       of the machine. In most cases, it is used to change from the multi-user
       state to another state.


       shutdown  must be run with an effective uid of 0, which may be provided
       by the Maintenance and Repair rights profile.


       By default, shutdown brings the system to a state where only  the  con‐
       sole  has  access to the operating system. This state is called single-
       user.


       Before starting to shut down daemons and  killing  processes,  shutdown
       sends  a  warning  message  and, by default, a final message asking for
       confirmation. message is a string that is sent out following the  stan‐
       dard warning message:

         The system will be shut down in ...



       If  the  string  contains  more  than  one word, it should be contained
       within single (') or double (") quotation marks.


       The warning message and the user provided message are output when there
       are 7200, 3600, 1800, 1200, 600, 300, 120, 60, and 30 seconds remaining
       before shutdown begins. See EXAMPLES.


       System state definitions are:

       state 0       Stop the operating system.


       state 1       State 1 is referred to as the  administrative  state.  In
                     state  1  file systems required for multi-user operations
                     are mounted, and logins requiring  access  to  multi-user
                     file  systems  can be used. When the system comes up from
                     firmware mode into state 1, only the  console  is  active
                     and  other multi-user (state 2) services are unavailable.
                     Note that not all user processes are stopped when transi‐
                     tioning from multi-user state to state 1.


       state s, S    State  s  (or S) is referred to as the single-user state.
                     All user processes are stopped  on  transitions  to  this
                     state.  In  the  single-user state, file systems required
                     for multi-user logins are unmounted and  the  system  can
                     only  be  accessed  through the console. Logins requiring
                     access to multi-user file systems cannot be used.


       state 5       Shut the machine down so that it is safe  to  remove  the
                     power.  Have  the  machine remove power, if possible. The
                     rc0 procedure is called to perform this task.


       state 6       Stop the operating system and reboot to the state defined
                     by  the initdefault entry in /etc/inittab. The rc6 proce‐
                     dure is called to perform this task.



       See init(8) for more information on the system run levels corresponding
       to these states.

OPTIONS
       -y

           Pre-answer  the  confirmation  question  so  the command can be run
           without user intervention.


       -g grace-period

           Specify the number of seconds to wait and warn users before switch‐
           ing states. If this option is not used, the default is 60 seconds.


       -i init-state

           Specify the init-state to change to at the end of the grace period,
           as if 'init  init-state' was run. By default, system state  's'  is
           used.


       -r

           Equivalent to specifying -i6.


       -p

           Reboots to prom. This flag can be used to reboot the system through
           firmware without changing the default reboot behavior as denoted by
           the  config/fastreboot_default property setting in the system/boot-
           config service.

           The -p and -i options are mutually exclusive.


EXAMPLES
       Example 1 Using shutdown



       In the following example, shutdown is being executed on host foo and is
       scheduled  in  120  seconds. The warning message is output 2 minutes, 1
       minute, and 30 seconds before the final confirmation message.


         example# shutdown -i S -g 120 "===== disk replacement ====="
         Shutdown started.   Tue Jun   7  14:51:40 PDT  1994

         Broadcast Message from root (pts/1) on foo Tue Jun  7 14:51:41...
         The system will be shut down in 2 minutes
         ===== disk replacement =====
         Broadcast Message from root (pts/1) on foo Tue Jun  7 14:52:41...
         The system will be shut down in 1 minutes
         ===== disk replacement =====
         Broadcast Message from root (pts/1) on foo Tue Jun  7 14:53:41...
         The system will be shut down in 30 seconds
         ===== disk replacement =====
         Do you want to continue? (y or n):


FILES
       /etc/inittab    controls process dispatching by init


ATTRIBUTES
       See attributes(7) for descriptions of the following attributes:


       tab() box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) ATTRIBUTE  TYPEAT‐
       TRIBUTE VALUE _ Availabilitysystem/core-os


SEE ALSO
       init.d(5),  inittab(5),  nologin(5),  attributes(7),  smf(7),  boot(8),
       bootadm(8), halt(8), init(8), killall(8), reboot(8)

NOTES
       When a system transitions down to run level 1 or single user (run level
       S or s), the /etc/nologin file (see nologin(5)) is created. Upon subse‐
       quent transition to run level  2,  3,  or  4  (multi-user  state),  the
       /etc/nologin file is removed.


       When  you  shut down an image, services are shut down in reverse depen‐
       dency order.



Oracle Solaris 11.4               3 Nov 2021                       shutdown(8)
맨 페이지 내용의 저작권은 맨 페이지 작성자에게 있습니다.
RSS ATOM XHTML 5 CSS3