Stop program going for startup in Linux
Slackware and also Arch linux have comparable approaches of stopping/starting procedures at boot, various than the Ubuntu and also Redhat - design instances offered over.
In both Slackware and also Arch linuxes, sh manuscripts exist in directory site
/etc/rc.d, commonly one manuscript per daemon, or one manuscript per subsystem.
As an example, Slackware begins the Apache internet server with a manuscript
/etc/rc.d/rc.httpd, called at the ideal time throughout system startup with an argument of "start". Arc linux has actually in different ways - called manuscripts, yet the very same type of point takes place.
To maintain some process from beginning throughout system boot, on Slackware, you simply make the ideal manuscript in/ etc/rc. d not executable. To maintain Apache from beginning at the next boot:
chmod -x /etc/rc.d/rc.httpd
To stop an Apache that got going at boot:
/etc/rc.d/rc.httpd stop You'll require to be origin.
Arc is a little bit extra intricate. The documents/ etc/rc. conf, a covering manuscript, has an array DAEMONS. To maintain Apache from beginning at boot, you would certainly transform this line in/ etc/rc. conf:
DAEMONS=(hal syslog-ng network netfs crond alsa sshd httpd ntpd postgresql)
To this line:
DAEMONS=(hal syslog-ng network netfs crond alsa sshd ntpd postgresql)
To stop a currently implementing apache, you would certainly execute
/etc/rc.d/httpd stop as origin.
If you are managing a modern-day Ubuntu system and also a couple of various other distros you might need to manage a mix of typical init manuscripts and also upstart manuscripts. Taking care of init manuscripts is covered by various other solutions. The following is one means to stop an upstart solution from beginning on boot:
# mv /etc/init/servicename.conf /etc/init/servicename.conf.disabled
The trouble with this method is that it does not permit you to start the solution making use of:
# service start servicename
A choice to this is to open the
servicename.conf documents in your favored editor and also comment out any kind of lines that start with:
That is, transform this to
#start on ...
where the "..." is whatever desired "start on" formerly. In this manner, when you intend to re - enable it, you do not need to remember what the "start on" parameters were.
Ultimately, if you have a new variation of startup you can merely add words "guidebook" throughout of the arrangement documents. You can do this straight from the covering:
# echo "manual" >> /etc/init/servicename.conf
This will certainly create startup to overlook any kind of "start on" expressions previously in the documents.
Depending on your distro make use of the chkconfig or upgrade - rc.d device to enable/disable system solutions.
On a redhat/suse/mandrake design system :
sudo chkconfig apache2 off
On Debian :
sudo update-rc.d -f apache2 remove
Check out their male web pages for even more details.