svcadm(8)을 검색하려면 섹션에서 8 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
init.d(5)
init.d(5) File Formats init.d(5)
NAME
init.d - initialization and termination scripts for changing init
states
SYNOPSIS
/etc/init.d
DESCRIPTION
/etc/init.d is a directory containing initialization and termination
scripts for changing init states. These scripts are linked when appro‐
priate to files in the rc?.d directories, where '?' is a single charac‐
ter corresponding to the init state. See init(8) for definitions of the
states.
The service management facility (see smf(7)) is the preferred mechanism
for service initiation and termination. The init.d and rc?.d directo‐
ries are obsolete, and are provided for compatibility purposes only.
Applications launched from these directories by svc.startd(8) are in‐
complete services, and are not restarted on failure.
File names in rc?.d directories are of the form [SK]nn<init.d file‐
name>, where S means start this job, K means kill this job, and nn is
the relative sequence number for killing or starting the job.
When entering a state (init S,0,2,3,etc.) the rc[S0-6] script executes
those scripts in /etc/rc[S0-6].d that are prefixed with K followed by
those scripts prefixed with S. When executing each script in one of the
/etc/rc[S0-6] directories, the /usr/sbin/rc[S0-6] script passes a sin‐
gle argument. It passes the argument 'stop' for scripts prefixed with K
and the argument 'start' for scripts prefixed with S. There is no harm
in applying the same sequence number to multiple scripts. In this case
the order of execution is deterministic but unspecified.
Guidelines for selecting sequence numbers are provided in README files
located in the directory associated with that target state. For exam‐
ple, /etc/rc[S0-6].d/README. Absence of a README file indicates that
there are currently no established guidelines.
Do not put /etc/init.d in your $PATH. Having this directory in your
$PATH can cause unexpected behavior. The programs in /etc/init.d are
associated with init state changes and, under normal circumstances, are
not intended to be invoked from a command line.
EXAMPLES
Example 1 Example of /usr/sbin/rc2.
When changing to init state 2 (multi-user mode, network resources not
exported), /sbin/rc2 is initiated by the svc.startd(8) process. The
following steps are performed by /usr/sbin/rc2.
1. In the directory /etc/rc2.d are files used to stop processes
that should not be running in state 2. The filenames are
prefixed with K. Each K file in the directory is executed
(by /usr/sbin/rc2) in alphanumeric order when the system en‐
ters init state 2. See example below.
2. Also in the rc2.d directory are files used to start
processes that should be running in state 2. As in Step 1,
each S file is executed.
Assume the file /etc/init.d/netdaemon is a script that initiates net‐
working daemons when given the argument 'start', and terminates the
daemons if given the argument 'stop'. It is linked to
/etc/rc2.d/S68netdaemon, and to /etc/rc0.d/K67netdaemon. The file is
executed by /etc/rc2.d/S68netdaemon start when init state 2 is entered
and by /etc/rc0.d/K67netdaemon stop when shutting the system down.
SEE ALSO
svcs(1), smf(7), init(8), svc.startd(8), svccfg(8)
NOTES
Solaris now provides an expanded mechanism, which includes automated
restart, for applications historically started using the init script
mechanism. The Service Management Facility (introduced in smf(7)) is
the preferred delivery mechanism for persistently running applications.
Existing init.d scripts continue to be executed according to the rules
in this manual page. The details of execution in relation to managed
services are available in svc.startd(8).
On earlier Solaris releases, a script named with a suffix of '.sh'
would be sourced, allowing scripts to modify the environment of other
scripts executed later. This behavior is no longer supported; for al‐
tering the environment in which services are run, see the setenv sub‐
command in svccfg(8).
Note that a script named with a suffix of '.sh' does not receive the
start or stop parameter that is received by the scripts which do not
have any suffix of '.sh'.
/usr/sbin/rc2 has references to the obsolescent rc.d directory. These
references are for compatibility with old INSTALL scripts. New INSTALL
scripts should use the init.d directory for related executables. The
same is true for the shutdown.d directory.
Oracle Solaris 11.4 24 Mar 2020 init.d(5)