Differences between revisions 27 and 28
Revision 27 as of 2011-07-03 19:35:44
Size: 3457
Comment:
Revision 28 as of 2011-07-03 19:41:15
Size: 3651
Comment: clarify servicename
Deletions are marked like this. Additions are marked like this.
Line 46: Line 46:
To (re)enable a service, using the default settings, run the following: To (re)enable a service (using the default settings) run the following command, where ''<servicename>'' corresponds to the name of the init script as listed in {{{/etc/init.d/}}}:
Line 52: Line 52:
To disable a service, run the following in a terminal as root: To disable a service, run the following command, where ''<servicename>'' corresponds to the name of the init script as listed in {{{/etc/init.d/}}}:

Translation(s): English


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 command, where <servicename> corresponds to the name of the init script as listed in /etc/init.d/:

# update-rc.d <servicename> defaults

Disabling services

To disable a service, run the following command, where <servicename> corresponds to the name of the init script as listed in /etc/init.d/:

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

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

See also