Linux services - Revision history

Pio2pio: /* Overview init.d and upstart */

2019-04-15T18:00:00Z

Overview init.d and upstart

← Older revision		Revision as of 20:00, 15 April 2019
Line 5:		Line 5:
	Currently there are actually 2 different ways for software to be started as a service in Ubuntu. A service is defined here as a program run by the system in the background, as opposed to one started and run directly by the user.		Currently there are actually 2 different ways for software to be started as a service in Ubuntu. A service is defined here as a program run by the system in the background, as opposed to one started and run directly by the user.

	The traditional way to start services in Linux was to place a script in /etc/init.d, and then use the update-rc.d command (or in RedHat based distros, chkconfig) to enable/disable it. This command, btw, uses some mildly complicated logic to create symlinks in /etc/rc#.d, that control the order of starting services. If you run ls /etc/rc2.d you can see the order that services will be killed (K##xxxx) and started (S##xxxx).		The traditional way to start services in Linux was to place a script in <code>/etc/init.d</code>, and then use the update-rc.d command (or in RedHat based distros, chkconfig) to enable/disable it. This command, btw, uses some mildly complicated logic to create symlinks in <code>/etc/rc#.d</code>, that control the order of starting services. If you run ls <code>/etc/rc2.d</code> you can see the order that services will be killed (<code>K##xxxx</code>) and started (<code>S##xxxx</code>).

	The issue with that was that when booting the system, everything had to be done in serial, one thing after another, making system boot times really slow. Attempts were made to parallelize this, but they were haphazard and hard to take full advantage of. This was the main reason that Upstart was created.		The issue with that was that when booting the system, everything had to be done in serial, one thing after another, making system boot times really slow. Attempts were made to parallelize this, but they were haphazard and hard to take full advantage of. This was the main reason that Upstart was created.
Line 11:		Line 11:
	Upstart uses job definition files in /etc/init to define on what events a service should be started. So, while the system is booting, upstart processes various events, and then can start multiple services in parallel. This allows them to fully utilize the resources of the system, for instance, by starting a disk-bound service up while another CPU-bound service runs, or while the network is waiting for a dynamic IP address to be assigned.		Upstart uses job definition files in /etc/init to define on what events a service should be started. So, while the system is booting, upstart processes various events, and then can start multiple services in parallel. This allows them to fully utilize the resources of the system, for instance, by starting a disk-bound service up while another CPU-bound service runs, or while the network is waiting for a dynamic IP address to be assigned.

	You can see all of the upstart job files by running ls /etc/init/*.conf		You can see all of the upstart job files by running ls <code>/etc/init/*.conf</code>

	Let me just stop here and say that if you don't know what a service is, or what it does, DO NOT disable it!		Let me just stop here and say that if you don't know what a service is, or what it does, DO NOT disable it!

Pio2pio: /* Disable upstart service */

2019-04-15T17:58:33Z

Disable upstart service

@@ Line 45: / Line 45: @@
 Upstart job definitions do not have an update-rc.d command. To disable the job, you need to edit the job file directly to disable it. If you want to still be able to manually start it, then you need to comment out the 'start on' condition. Say you want to install samba, but not have it start automatically.. here is its job file (in natty):
 To disable it, you can just put a # in front of the 'start on local-filesystems'. Note that while it won't start back up on boot, you still need to stop it this time with
- sudo service smbd stop
+<source lang=bash>
 If, however, you never want it to start, I'd suggest actually removing the package. If, however, you want it installed, but not startable, you can also do:
- mv /etc/init/smbd.conf /etc/init/smbd.conf.disabled
+<source lang=bash>
 = CentOS - RPM based =

Pio2pio: /* RPM based - service managment */

2019-04-15T17:56:43Z

RPM based - service managment

← Older revision		Revision as of 19:56, 15 April 2019
Line 66:		Line 66:
	mv /etc/init/smbd.conf /etc/init/smbd.conf.disabled		mv /etc/init/smbd.conf /etc/init/smbd.conf.disabled

	= RPM based ~~- service managment~~ =		= CentOS - RPM based =
	<source lang=bash>		<source lang=bash>
	sudo chkconfig --list all		sudo chkconfig --list all

Pio2pio: /* Working with services */

2019-04-15T17:56:14Z

Working with services

← Older revision		Revision as of 19:56, 15 April 2019
Line 1:		Line 1:
	This is a begging of the working with Linux services also read daemons 'd' programs.		This is a begging of the working with Linux services also read daemons 'd' programs.

	~~= Working with services =~~

	= Ubuntu - Debian based =		= Ubuntu - Debian based =

Pio2pio: /* Overview init.d and upstart */

2019-04-15T17:56:03Z

Overview init.d and upstart

← Older revision		Revision as of 19:56, 15 April 2019
Line 3:		Line 3:
	= Working with services =		= Working with services =

			= Ubuntu - Debian based =
	== Overview init.d and upstart ==		== Overview init.d and upstart ==
	Currently there are actually 2 different ways for software to be started as a service in Ubuntu. A service is defined here as a program run by the system in the background, as opposed to one started and run directly by the user.		Currently there are actually 2 different ways for software to be started as a service in Ubuntu. A service is defined here as a program run by the system in the background, as opposed to one started and run directly by the user.

Pio2pio: /* References */

2019-04-15T17:55:23Z

References

← Older revision		Revision as of 19:55, 15 April 2019
Line 81:		Line 81:

	= References =		= References =
			*[https://www.thegeekdiary.com/how-to-enable-or-disable-service-on-boot-with-chkconfig/ chkconfig] basics

Pio2pio: /* RPM based - service managment */

2019-04-15T17:50:33Z

RPM based - service managment

← Older revision		Revision as of 19:50, 15 April 2019
Line 76:		Line 76:

	sudo chkconfig collectd on #enable		sudo chkconfig collectd on #enable

			sudo chkconfig [servicename] reset #reset to a service defaults
	</source>		</source>

	= References =		= References =

Pio2pio: /* References */

2019-04-15T17:34:33Z

References

← Older revision		Revision as of 19:34, 15 April 2019
Line 67:		Line 67:
	mv /etc/init/smbd.conf /etc/init/smbd.conf.disabled		mv /etc/init/smbd.conf /etc/init/smbd.conf.disabled

			= RPM based - service managment =
			<source lang=bash>
			sudo chkconfig --list all

			sudo chkconfig collectd off #disable
			[ec2-user@server1]$ chkconfig --list \| grep collectd
			collectd 0:off 1:off 2:off 3:off 4:off 5:off 6:off

			sudo chkconfig collectd on #enable
			</source>
	= References =		= References =

Pio2pio: /* Overview init.d and upstart */

2014-12-30T23:41:01Z

Overview init.d and upstart

← Older revision		Revision as of 01:41, 31 December 2014
Line 3:		Line 3:
	= Working with services =		= Working with services =

	= Overview init.d and upstart =		== Overview init.d and upstart ==
	Currently there are actually 2 different ways for software to be started as a service in Ubuntu. A service is defined here as a program run by the system in the background, as opposed to one started and run directly by the user.		Currently there are actually 2 different ways for software to be started as a service in Ubuntu. A service is defined here as a program run by the system in the background, as opposed to one started and run directly by the user.

Line 17:		Line 17:

	Not all services have been converted to upstart. While working on the server team at Canonical for the past few months, I've worked on a number of converted job files, and the nicest part is that it allows one to get rid of all the script "magic" and just put in a few commands here and there to define exactly how to start the service, and nothing more. But for now, only a handful of traditional network services, like squid and samba, have been converted.		Not all services have been converted to upstart. While working on the server team at Canonical for the past few months, I've worked on a number of converted job files, and the nicest part is that it allows one to get rid of all the script "magic" and just put in a few commands here and there to define exactly how to start the service, and nothing more. But for now, only a handful of traditional network services, like squid and samba, have been converted.


	== Check if it's an upstart service ==		== Check if it's an upstart service ==

Pio2pio: Created page with "This is a begging of the working with Linux services also read daemons 'd' programs. = Working with services = = Overview init.d and upstart = Currently there are actually 2..."

2014-12-30T23:33:28Z

Created page with "This is a begging of the working with Linux services also read daemons 'd' programs. = Working with services = = Overview init.d and upstart = Currently there are actually 2..."

New page

This is a begging of the working with Linux services also read daemons 'd' programs.

= Working with services =

= Overview init.d and upstart =
Currently there are actually 2 different ways for software to be started as a service in Ubuntu. A service is defined here as a program run by the system in the background, as opposed to one started and run directly by the user.

The traditional way to start services in Linux was to place a script in /etc/init.d, and then use the update-rc.d command (or in RedHat based distros, chkconfig) to enable/disable it. This command, btw, uses some mildly complicated logic to create symlinks in /etc/rc#.d, that control the order of starting services. If you run ls /etc/rc2.d you can see the order that services will be killed (K##xxxx) and started (S##xxxx).

The issue with that was that when booting the system, everything had to be done in serial, one thing after another, making system boot times really slow. Attempts were made to parallelize this, but they were haphazard and hard to take full advantage of. This was the main reason that Upstart was created.

Upstart uses job definition files in /etc/init to define on what events a service should be started. So, while the system is booting, upstart processes various events, and then can start multiple services in parallel. This allows them to fully utilize the resources of the system, for instance, by starting a disk-bound service up while another CPU-bound service runs, or while the network is waiting for a dynamic IP address to be assigned.

You can see all of the upstart job files by running ls /etc/init/*.conf

Let me just stop here and say that if you don't know what a service is, or what it does, DO NOT disable it!

Not all services have been converted to upstart. While working on the server team at Canonical for the past few months, I've worked on a number of converted job files, and the nicest part is that it allows one to get rid of all the script "magic" and just put in a few commands here and there to define exactly how to start the service, and nothing more. But for now, only a handful of traditional network services, like squid and samba, have been converted.

== Check if it's an upstart service ==
In order to figure out if a service is upstart based, you can run the status command:
status servicename

If its an upstart job, it will show this:
$ status statd
statd start/running, process 942

But if its not, you'll see something more like this:
$ status apache2
status: Unknown job: apache2

In this case, apache2 has not been converted to upstart. So, to disable apache2 you just run
sudo update-rc.d apache2 disable
sudo service apache2 stop

== Disable upstart service ==
Starting with the version of upstart that will be in 11.04, there is a new keyword that disables the '''start on''' and '''stop on''' stanzas, it is '''manual'''. So another way to disable the service as of 11.04 is to do:

command using sudo
echo 'manual' | sudo tee /etc/init/mysql.override

command from root shell
echo manual >> /etc/init/mysql.override

;OBSOLETE since Ubuntu 11.04

Upstart job definitions do not have an update-rc.d command. To disable the job, you need to edit the job file directly to disable it. If you want to still be able to manually start it, then you need to comment out the 'start on' condition. Say you want to install samba, but not have it start automatically.. here is its job file (in natty):

description "SMB/CIFS File Server"
author "Steve Langasek <steve.langasek@ubuntu.com>"

start on local-filesystems
stop on runlevel [!2345]
respawn
pre-start script
RUN_MODE="daemons"
[ -r /etc/default/samba ] && . /etc/default/samba
[ "$RUN_MODE" = inetd ] && { stop; exit 0; }
install -o root -g root -m 755 -d /var/run/samba
end script
exec smbd -F

To disable it, you can just put a # in front of the 'start on local-filesystems'. Note that while it won't start back up on boot, you still need to stop it this time with
sudo service smbd stop

If, however, you never want it to start, I'd suggest actually removing the package. If, however, you want it installed, but not startable, you can also do:
mv /etc/init/smbd.conf /etc/init/smbd.conf.disabled

= References =