Differences between revisions 24 and 26 (spanning 2 versions)
Revision 24 as of 2011-07-03 18:24:40
Size: 3146
Comment:
Revision 26 as of 2011-07-03 19:34:30
Size: 3482
Comment:
Deletions are marked like this. Additions are marked like this.
Line 12: Line 12:
== Managing daemons in Debian == == Daemons in Debian ==
Line 15: Line 15:
''Note: Many daemons provide essential services to a working Debian installation; others can pose unnecessary security risks when enabled carelessly. Caution should be used whenever managing daemons. When in doubt, refer to the documentation of the daemon itself.'' == Managing Daemons ==
=== A brief introduction to Debian init scripts ===
Daemon init scripts are stored in {{{/etc/init.d/}}}
Line 17: Line 19:
=== Common tasks === When a daemon is enabled or disabled, symbolic links targeting the respective init script are created or removed under the various {{{/etc/rc*.d/}}} directories, corresponding to the RunLevel(s) in which the daemon is to run.

To view a list of currently available services:
{{{
$ ls /etc/init.d
}}}

=== Common service tasks ===
Line 23: Line 32:
A brief description of each option follows: A brief description of the most common options follows:
Line 30: Line 39:
Stopping and starting daemons in this manner is temporary and will not survive a reboot. Refer to the next section to enable/disable daemons on a more permanent basis. Starting and stopping daemons in this manner is temporary and will not survive a reboot. Refer to the next section to enable/disable daemons on a permanent basis.
Line 32: Line 41:
=== Add/remove daemons ===
The terms ''add'' and ''remove'' are a bit of a misnomer because we're not actually adding or removing the services from Debian, rather we're enabling or disabling them.
=== Enable/disable daemons ===
''Note: Many daemons provide essential services to a working Debian installation; others can pose unnecessary security risks when enabled carelessly. Caution should be used whenever managing daemons. When in doubt, refer to the documentation of the daemon itself.''
Line 35: Line 44:
Several tools exist to manage system services, including DebianPkg:rcconf and DebianPkg:sys-v-conf. The default tool however is '''update-rc.d'''. Several tools exist to manage system services, including DebianPkg:rcconf and DebianPkg:sys-v-conf. The default tool however is '''update-rc.d''' and that is what the following examples use.

==== Enabling services ====
To (re)enable a service, using the default settings, run the following:
{{{
# update-rc.d <servicename> defaults
}}}
Line 43: Line 58:
==== Enabling services ====
To (re)enable a service, using the default settings, run the following:
{{{
# update-rc.d <servicename> defaults
}}}

For detailed information on what these commands do, refer to the '''update-rc.d''' manpage.
For more detail on what these commands do, refer to the [[DebianMan:8/update-rc.d|update-rc.d manpage]].

Translation(s): English


What is a daemon?

A daemon, or system service, is a background process usually started during the initial boot sequence by ?init. Daemons typically run independent of users, waiting for system events to occur and providing services in response. Some common daemons include:

  • sshd - listens for and manages incoming ?SSH connections

  • acpid - listens for power management events and executes scripts based on them

  • apache - provides a local HTTP web server

Daemons in Debian

Debian makes use of System V-style init scripts for daemon management. This allows daemons to operate conditionally, based on the current RunLevel of the computer. For example, a daemon can be configured to run only when the computer is in single-user mode (runlevel 1) or, more commonly, when in multi-user mode (runlevels 2-5). For more information, see ?init and RunLevel.

Managing Daemons

A brief introduction to Debian init scripts

Daemon init scripts are stored in /etc/init.d/

When a daemon is enabled or disabled, symbolic links targeting the respective init script are created or removed under the various /etc/rc*.d/ directories, corresponding to the RunLevel(s) in which the daemon is to run.

To view a list of currently available services:

$ ls /etc/init.d

Common service tasks

Most system services accept a common set of options, which can be passed directly to the daemon script at the command line, for example:

# /etc/init.d/ssh restart
Restarting OpenBSD Secure Shell server: sshd.

A brief description of the most common options follows:

  • start: start a service

  • stop: stop a service

  • restart: restart a service without reloading its job config file

  • reload: send a SIGHUP signal to running process

  • status: return the status of a service

Starting and stopping daemons in this manner is temporary and will not survive a reboot. Refer to the next section to enable/disable daemons on a permanent basis.

Enable/disable daemons

Note: Many daemons provide essential services to a working Debian installation; others can pose unnecessary security risks when enabled carelessly. Caution should be used whenever managing daemons. When in doubt, refer to the documentation of the daemon itself.

Several tools exist to manage system services, including rcconf and sys-v-conf. The default tool however is update-rc.d and that is what the following examples use.

Enabling services

To (re)enable a service, using the default settings, run the following:

# update-rc.d <servicename> defaults

Disabling services

To disable a service, run the following in a terminal as root:

# update-rc.d -f <servicename> remove

For more detail on what these commands do, refer to the update-rc.d manpage.

See also