09-20-2002
init.d contains a bunch of scripts. that can be use to start or stop a daemon or application while the server is up and running or during boot or when entering another runlevel. Services or daemon that can be started could include things like networking, nfs, sendmail, apache.
init.d script is link through a symbolly link to rc script (run control script)
eg In the /etc/rc3.d directory shows
S60nfs -> ../init.d/nfs
lrwxrwxrwx 1 root root 15 13:11 S70nfsfs -> ../init.d/nfsfs
lrwxrwxrwx 1 root root 23 13:11 S80sendmail -> ../init.d/sendmail.init
when your system enter run level 3 or boot up in mult user mode
init.d start up applications or daemons in mult user mode.
when your system is shutdown init.d excute script in /etc/rc0.d which shutdown the application before your system goes down.
script in /etc/rc0.d start with K which indicate kill script
Note
S indicate a start up script in /etc/rc2.d or /etc/rc3.d while K indicate kill script in your /etc/rc0.d
so init.d shutdown down application and starts applications automatically.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have written a daemon and want to make sure that it starts up again after the machine is re-started so I can quit manually doing it. Problem is I'm having difficulty understanding what to do with the init.d
Any help would be appreciated! (1 Reply)
Discussion started by: BC_Kevin
1 Replies
2. UNIX for Advanced & Expert Users
Hi Expert,
I have encountered some problem with my SUN system. Everytime when i issue command #init 6 OR #init 0 it just logout and prompt for login again instead of rebooting the server when run init 6 and system shutdown when run init 0..
I can only reboot the system using reboot ... Was... (6 Replies)
Discussion started by: sc2005
6 Replies
3. UNIX for Dummies Questions & Answers
Hi all,
What should i do to make the following work:
# /etc/init.d/networking restart
Setting up IP spoofing protection: rp_filter.
Reconfiguring network interfaces...No support for INET6 on this system.
Failed to bring up lo.
done.
Thanks & Regards
Gauri (0 Replies)
Discussion started by: gauri
0 Replies
4. Solaris
root@test09 # ls -al /sbin/init
-r-xr-xr-x 1 root sys 550000 Jun 29 2002 /sbin/init
root@test09 # ls -al /usr/sbin/init
-r-xr-xr-x 1 root sys 37100 Jun 29 2002 /usr/sbin/init (2 Replies)
Discussion started by: userking
2 Replies
5. UNIX for Dummies Questions & Answers
I know if a parent process exits before its child, the last one becomes orphan for a while and then is added to the children of Init process.
I'd like to know deeper
1 how the orphan becomes init process,
2 how init knows that from a some point on it has another child.
Thank you in advance. (2 Replies)
Discussion started by: Puntino
2 Replies
6. Linux
Dear all,
I typed in init 1 on my redhat box as root and according to wikipedia (http://en.wikipedia.org/wiki/Runlevel):
1 Single-User Mode Does not configure network interfaces, start daemons, or allow non-root logins
So now I can't connect back to it. How do I change the init back to 3?... (8 Replies)
Discussion started by: z1dane
8 Replies
7. Red Hat
What is the difference between 'init s' and 'init 1'.
I know that both will work to change the current run level to single user mode.
Is there any difference in those two commands? (5 Replies)
Discussion started by: praveen_b744
5 Replies
8. UNIX for Advanced & Expert Users
Hi,
I am experiencing a weird thing on my SUNFIRE machine with Solaris 9 OS.
When I do init 0 to shutdown the machine to go to ok prompt, what it did was shutdown and reboot like an init 6 command do. I did check the corresponding rc scripts that were involved with init 0 and compared with rc... (2 Replies)
Discussion started by: Yenthanh
2 Replies
9. Solaris
i did my research in finding the answer but couldn't find right one. Please give your inputs. (6 Replies)
Discussion started by: ranumala
6 Replies
10. Red Hat
I encountered a problem on one of our database servers.
OS: CentOS 5.5 final
Kernel: 2.6.18-238.5.1.el5.028stab085.2 (OpenVZ kernel)
We wrote some DB-Start/Stop-scripts ("/db2/admin/scripts_dba/start_services.ksh" and ".../stop_services.ksh") to start the database instances. (Database... (1 Reply)
Discussion started by: bakunin
1 Replies
LEARN ABOUT MOJAVE
init.d
init.d(4) init.d(4)
NAME
init.d - initialization and termination scripts for changing init states
SYNOPSIS
/etc/init.d
/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 character corresponding to the init state. See init(1M) for definitions of
the states.
The service management facility (see smf(5)) is the preferred mechanism for service initiation and termination. The init.d and rc?.d direc-
tories are obsolete, and are provided for compatibility purposes only. Applications launched from these directories by svc.startd(1M) are
incomplete services, and will not be restarted on failure.
File names in rc?.d directories are of the form [SK]nn<init.d filename>, 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 /sbin/rc[S0-6] script passes a
single 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
example, /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.
Example 1: Example of /sbin/rc2.
When changing to init state 2 (multi-user mode, network resources not exported), /sbin/rc2 is initiated by the svc.startd(1M) process. The
following steps are performed by /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 /sbin/rc2) in alphanumeric order when the system enters 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 will initiate networking daemons when given the argument 'start', and will terminate
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.
svcs(1), init(1M), svc.startd(1M), svccfg(1M), smf(5)
Solaris now provides an expanded mechanism, which includes automated restart, for applications historically started via the init script
mechanism. The Service Management Facility (introduced in smf(5)) is the preferred delivery mechanism for persistently running applica-
tions. Existing init.d scripts will, however, 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(1M).
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 altering the environment in which services are run, see the setenv sub-
command in svccfg(1M).
/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.
17 Aug 2005 init.d(4)