Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
The ONE Campaign to make poverty history

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 176 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here







       The  scripts  for  controlling  the  system  are placed in
       /etc/init.d/ (they have  been  moved  accordingly  to  the
       Linux  Standard  Base (LSB) specification).  These scripts
       are executed directly or  indirectly  by  /sbin/init,  the
       father  of  all processes. The configuration of /sbin/init
       is given by the file /etc/inittab (see inittab(5)).

       At   boot   time,   the   boot   level    master    script
       /etc/init.d/boot  is called to initialise the system (e.g.
       file system check, ...).  It also executes  some  hardware
       init  scripts  linked  into  /etc/init.d/boot.d/.  Then it
       calls /etc/init.d/boot.local,  which  executes  the  local

       After  system  startup, /sbin/init will normally switch on
       the default run level given in /etc/inittab.  It calls the
       run  level  master  script /etc/init.d/rc to start or stop
       services provided by the other scripts under /etc/init.d/.

       To  control the services of a run level, the corresponding
       scripts   are   linked   into   run   level    directories
       /etc/init.d/rc<X>.d/, where <X>=0,1,2,3,4,5,6,S is the run
       level number.

       There are two kinds of symbolic link: start  links,  which
       are  called  when  entering  a  run level, and stop links,
       which are called when leaving a run level.  Note that each
       service  in  the  run  levels 2, 3, 4, and 5 consists of a
       start and a stop link.  Within SuSE boot concept a differ­
       ential link scheme is used to be able to change a runlevel
       in comparision with the former level.

       To avoid redundant starts when changing  run  levels  only
       those  services  are  started, which have no start link in
       the previous run level.  And to avoid redundant stops when
       changing run levels, only those services are stopped which
       have no start link in the current level. To  control  this
       behaviour, the names of the scripts are added on the names
       of the start and stop links.

       To control the order of  service  starts  and  stops,  the
       start  and stop links include a number in their link name.

       The system configuration files in  /etc/sysconfig  contain
       most of the variables used to configure the installed ser­
       vices.  These variables can easily be changed by  YaST  or
       To  do  this  automatically in run level 3, this script is
       linked into /etc/init.d/rc3.d/  with  these  two  symbolic

              /etc/init.d/rc3.d/S20lpd -> ../lpd

              /etc/init.d/rc3.d/K20lpd -> ../lpd

       The  corresponding link with the letter S is used to start
       a service. For the printing service the number between the
       letter S and the name should be greater than the number of
       the start link of the network service.  The  corresponding
       link with the letter K is used to stop a service. The num­
       ber of the stop link for the printing  service  should  be
       less than that of the stop link for the network service so
       that the printer daemon is stopped  before  shutting  down
       the network service.

   Run levels and their services
       0      This level is used for halting the system. The only
              valid service for this level is  the  script  halt,
              which   is  linked  into  /etc/init.d/rc0.d/.   The
              script halt executes /etc/init.d/halt.local.   Spe­
              cials  system  issues  for halt or reboot should be
              added there.

       6      This level is used for rebooting  the  system.  The
              only  valid  service  for  this level is the script
              reboot, which is  linked  into  /etc/init.d/rc6.d/.
              The  script reboot executes /etc/init.d/halt.local.
              Specials system issues for halt or reboot should be
              added there.

       S      This  mode  is  used to switch from boot phase into
              single user mode.  The last valid service for  this
              mode  is  the  script  single, which is linked into
              /etc/init.d/rcS.d/.  In this mode you have only one

       1      Accordingly to the Linux Standard Base (LSB) speci­
              fication this runlevel is used to switch from  nor­
              mal  runlevel  into single user mode.  This is dif­
              ferent from former SuSE Linux versions!

       2      The run level 2 is without remote networking.  Note
              that  on  some other systems this is identical with
              the single user mode.  This run level can have more
              than one virtual console.

       3      The  run level 3 is with network. This run level is
              for server stations not automatically running X.



       insserv(8), init(8), inittab(5), and the SuSE Linux  hand­
       book, chapter The SuSE boot concept.


       1996-2002 SuSE Linux AG, Nuernberg, Germany.


       Florian  La  Roche  <http://www.suse.de/feedback>,  Werner
       Fink      <werner@suse.de>,       Burchard       Steinbild

Version 0.4                Nov 15, 2000                 INIT.D(7)

An undefined database error occurred. SELECT distinct pages.pagepath,pages.pageid FROM pages, page2command WHERE pages.pageid = page2command.pageid AND commandid =

Show your Support for the Linux Tutorial

Purchase one of the products from our new online shop. For each product you purchase, the Linux Tutorial gets a portion of the proceeds to help keep us going.



Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
You can get all the latest Site and Linux news by checking out our news page.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds