How do I stop Apache2 from automatically starting on boot?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
How do I stop Apache2 from automatically starting on boot? I can't seem to find an option that disables the automatic start-up when I turn on the machine.
apache2 systemd init.d
edited Mar 27 at 3:19
yourcomputergenius
74
asked Aug 1 '12 at 2:11
niccolo m.niccolo m.
9563912
add a comment |
How do I stop Apache2 from automatically starting on boot? I can't seem to find an option that disables the automatic start-up when I turn on the machine.
apache2 systemd init.d
edited Mar 27 at 3:19
yourcomputergenius
74
asked Aug 1 '12 at 2:11
niccolo m.niccolo m.
9563912
1
Perhaps someone can be more specific, but I can point you in the right direction... in /etc, there are directories for rc*.d, which contain all the start/stop scripts, called, I think, init scripts. You'll see links to scripts that are in /etc/init.d, and starting with either "k" or "s", for "kill" or "start", and a number which is the ordering.
– Marty Fried
Aug 1 '12 at 2:27
Yes, I knew about the /etc/rcX.d directories, but I searched for it to find out about some nicer tool, than just manually renaming files (life is too short).update-rc.dhas filled this void.
– Tomasz Gandor
Sep 26 '14 at 8:53
add a comment |
How do I stop Apache2 from automatically starting on boot? I can't seem to find an option that disables the automatic start-up when I turn on the machine.
apache2 systemd init.d
edited Mar 27 at 3:19
yourcomputergenius
74
asked Aug 1 '12 at 2:11
niccolo m.niccolo m.
9563912
How do I stop Apache2 from automatically starting on boot? I can't seem to find an option that disables the automatic start-up when I turn on the machine.
apache2 systemd init.d
apache2 systemd init.d
edited Mar 27 at 3:19
yourcomputergenius
74
asked Aug 1 '12 at 2:11
niccolo m.niccolo m.
9563912
edited Mar 27 at 3:19
yourcomputergenius
74
asked Aug 1 '12 at 2:11
niccolo m.niccolo m.
9563912
edited Mar 27 at 3:19
yourcomputergenius
74
edited Mar 27 at 3:19
yourcomputergenius
74
edited Mar 27 at 3:19
yourcomputergenius
74
74
asked Aug 1 '12 at 2:11
niccolo m.niccolo m.
9563912
asked Aug 1 '12 at 2:11
niccolo m.niccolo m.
9563912
asked Aug 1 '12 at 2:11
niccolo m.niccolo m.
9563912
9563912
1
Perhaps someone can be more specific, but I can point you in the right direction... in /etc, there are directories for rc*.d, which contain all the start/stop scripts, called, I think, init scripts. You'll see links to scripts that are in /etc/init.d, and starting with either "k" or "s", for "kill" or "start", and a number which is the ordering.
– Marty Fried
Aug 1 '12 at 2:27
Yes, I knew about the /etc/rcX.d directories, but I searched for it to find out about some nicer tool, than just manually renaming files (life is too short).update-rc.dhas filled this void.
– Tomasz Gandor
Sep 26 '14 at 8:53
add a comment |
1
Perhaps someone can be more specific, but I can point you in the right direction... in /etc, there are directories for rc*.d, which contain all the start/stop scripts, called, I think, init scripts. You'll see links to scripts that are in /etc/init.d, and starting with either "k" or "s", for "kill" or "start", and a number which is the ordering.
– Marty Fried
Aug 1 '12 at 2:27
Yes, I knew about the /etc/rcX.d directories, but I searched for it to find out about some nicer tool, than just manually renaming files (life is too short).update-rc.dhas filled this void.
– Tomasz Gandor
Sep 26 '14 at 8:53
1
1
Perhaps someone can be more specific, but I can point you in the right direction... in /etc, there are directories for rc*.d, which contain all the start/stop scripts, called, I think, init scripts. You'll see links to scripts that are in /etc/init.d, and starting with either "k" or "s", for "kill" or "start", and a number which is the ordering.
– Marty Fried
Aug 1 '12 at 2:27
Perhaps someone can be more specific, but I can point you in the right direction... in /etc, there are directories for rc*.d, which contain all the start/stop scripts, called, I think, init scripts. You'll see links to scripts that are in /etc/init.d, and starting with either "k" or "s", for "kill" or "start", and a number which is the ordering.
– Marty Fried
Aug 1 '12 at 2:27
Yes, I knew about the /etc/rcX.d directories, but I searched for it to find out about some nicer tool, than just manually renaming files (life is too short).
update-rc.d has filled this void.– Tomasz Gandor
Sep 26 '14 at 8:53
Yes, I knew about the /etc/rcX.d directories, but I searched for it to find out about some nicer tool, than just manually renaming files (life is too short).
update-rc.d has filled this void.– Tomasz Gandor
Sep 26 '14 at 8:53
add a comment |
4 Answers
4
active
oldest
votes
Under the folder /etc/init.d/ you will find all the init scripts for different boot up services, like apache2, networking, etc.
Depending on which runlevel the computer starts in, different services are started.
So from the /etc/init.d/ folder each "service" is linked to one/many/no run level folders named from rc0.d to rc6.d.
To keep things simple there is a tool for removing/adding these links, hence removing or adding scripts to and from start up.
To disable apache2 simply type:
sudo update-rc.d apache2 disable
This disables apache2 at startup but is not removed so it can be enabled again. To remove the apache2 startup scripts do the following:
To remove apache2 simply type:
sudo update-rc.d -f apache2 remove
Doing this will cause all runlevel folders that are linked to apache2 to be removed.
edited Feb 4 '18 at 13:46
MDijkstra
32
answered Aug 1 '12 at 2:47
tomodachitomodachi
9,70242343
2
chkconfig may also help - " chkconfig {service_name} off "
– MCR
Aug 1 '12 at 7:10
Doesn't work anymore:The script you are attempting to invoke has been converted to an Upstart job, but lsb-header is not supported for Upstart jobs. (...)
– TomDogg
Apr 29 '15 at 9:34
2
@TomDogg, can you specify the versions you were working with? This answer works for Apache 2 on Ubuntu 14.04.3
– Dale Anderson
Nov 2 '15 at 20:20
1
How to restore the service?
– Eugen Konkov
Apr 14 '16 at 8:12
9
Warning! This will REMOVE the service! Usesudo update-rc.d apache2 disable.
– Eduardo Cuomo
Jan 17 '17 at 19:37
|
show 2 more comments
you could simply disable it by:
sudo update-rc.d apache2 disable
and then if you would like to enable it again:
sudo update-rc.d apache2 enable
depending on the project i am working on, it is handy to have the service conveniently available, if i wish to re-enable it.
edited Dec 10 '14 at 18:47
tomodachi
9,70242343
answered Oct 8 '13 at 0:08
gsullinsgsullins
2,009173
4
enablegave me an error likerunlevel arguments (none) do not match LSB Default-Start values, butsudo update-rc.d apache2 defaultsappears to have re-enabled it successfully.
– here
Jan 13 '14 at 3:58
2
@heresudo update-rc.d apache2 enableplayed as expected for me
– Georgios Pligoropoulos
Feb 9 '14 at 15:12
1
On Ubuntu Trusty it tells me "The disable|enable API is not stable and might change in the future."
– Tanner
Jun 10 '14 at 0:31
1
Doesn't work -error: no runlevel symlinks to modify, aborting!. However, apache2 is running and autostarts.
– Daniel Kmak
Dec 14 '14 at 11:05
Doesn't work anymore:update-rc.d: error: no runlevel symlinks to modify, aborting!
– TomDogg
Apr 29 '15 at 9:33
|
show 5 more comments
With systemd we can now use systemctl commands to prevent a service from automatically starting at boot.
here is an example:
sudo systemctl disable apache2
You will still be able to start and stop the service but it won't start up at boot.
answered Sep 18 '15 at 22:20
mchidmchid
23.7k25287
2
Linux Mint is still based on Ubuntu 14.04. Ubuntu starts using systemd from 15.04 on.
– twan163
Dec 6 '15 at 23:01
1
@dragonmnl as twan163 said, systemd is for the newer versions (debian jessie or equivalent +)
– mchid
Dec 8 '15 at 21:55
1
this worked great on Debian
– Anupam
Jul 19 '17 at 12:37
1
the right answer for debian 9+
– John
Nov 24 '17 at 5:12
1
If encounterupdate-rc.d: error: no runlevel symlinks to modify, aborting!, recreate any below missing simlinks; then retry: /etc/rc0.d/K01<service> /etc/rc1.d/K01<service> /etc/rc2.d/S99<service> /etc/rc3.d/S99<service> /etc/rc4.d/S99<service> /etc/rc5.d/S99<service> /etc/rc6.d/K01<service>
– Amil Waduwawara
Aug 11 '18 at 2:26
|
show 3 more comments
Thought I'd just add to the answers by @gsullins and @tomodachi, for future readers who used the accepted answer.
If you've already used:
sudo update-rc.d apache2 remove
You can use the argument defaults to add apache2 back into the autostart
sudo update-rc.d apache2 defaults
Then you're able to enable/disable
sudo update-rc.d apache2 disable
sudo update-rc.d apache2 enable
answered Mar 1 '17 at 0:10
Ben WindingBen Winding
37329
add a comment |
protected by Byte Commander Mar 3 '16 at 12:27
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Under the folder /etc/init.d/ you will find all the init scripts for different boot up services, like apache2, networking, etc.
Depending on which runlevel the computer starts in, different services are started.
So from the /etc/init.d/ folder each "service" is linked to one/many/no run level folders named from rc0.d to rc6.d.
To keep things simple there is a tool for removing/adding these links, hence removing or adding scripts to and from start up.
To disable apache2 simply type:
sudo update-rc.d apache2 disable
This disables apache2 at startup but is not removed so it can be enabled again. To remove the apache2 startup scripts do the following:
To remove apache2 simply type:
sudo update-rc.d -f apache2 remove
Doing this will cause all runlevel folders that are linked to apache2 to be removed.
edited Feb 4 '18 at 13:46
MDijkstra
32
answered Aug 1 '12 at 2:47
tomodachitomodachi
9,70242343
2
chkconfig may also help - " chkconfig {service_name} off "
– MCR
Aug 1 '12 at 7:10
Doesn't work anymore:The script you are attempting to invoke has been converted to an Upstart job, but lsb-header is not supported for Upstart jobs. (...)
– TomDogg
Apr 29 '15 at 9:34
2
@TomDogg, can you specify the versions you were working with? This answer works for Apache 2 on Ubuntu 14.04.3
– Dale Anderson
Nov 2 '15 at 20:20
1
How to restore the service?
– Eugen Konkov
Apr 14 '16 at 8:12
9
Warning! This will REMOVE the service! Usesudo update-rc.d apache2 disable.
– Eduardo Cuomo
Jan 17 '17 at 19:37
|
show 2 more comments
Under the folder /etc/init.d/ you will find all the init scripts for different boot up services, like apache2, networking, etc.
Depending on which runlevel the computer starts in, different services are started.
So from the /etc/init.d/ folder each "service" is linked to one/many/no run level folders named from rc0.d to rc6.d.
To keep things simple there is a tool for removing/adding these links, hence removing or adding scripts to and from start up.
To disable apache2 simply type:
sudo update-rc.d apache2 disable
This disables apache2 at startup but is not removed so it can be enabled again. To remove the apache2 startup scripts do the following:
To remove apache2 simply type:
sudo update-rc.d -f apache2 remove
Doing this will cause all runlevel folders that are linked to apache2 to be removed.
edited Feb 4 '18 at 13:46
MDijkstra
32
answered Aug 1 '12 at 2:47
tomodachitomodachi
9,70242343
2
chkconfig may also help - " chkconfig {service_name} off "
– MCR
Aug 1 '12 at 7:10
Doesn't work anymore:The script you are attempting to invoke has been converted to an Upstart job, but lsb-header is not supported for Upstart jobs. (...)
– TomDogg
Apr 29 '15 at 9:34
2
@TomDogg, can you specify the versions you were working with? This answer works for Apache 2 on Ubuntu 14.04.3
– Dale Anderson
Nov 2 '15 at 20:20
1
How to restore the service?
– Eugen Konkov
Apr 14 '16 at 8:12
9
Warning! This will REMOVE the service! Usesudo update-rc.d apache2 disable.
– Eduardo Cuomo
Jan 17 '17 at 19:37
|
show 2 more comments
Under the folder /etc/init.d/ you will find all the init scripts for different boot up services, like apache2, networking, etc.
Depending on which runlevel the computer starts in, different services are started.
So from the /etc/init.d/ folder each "service" is linked to one/many/no run level folders named from rc0.d to rc6.d.
To keep things simple there is a tool for removing/adding these links, hence removing or adding scripts to and from start up.
To disable apache2 simply type:
sudo update-rc.d apache2 disable
This disables apache2 at startup but is not removed so it can be enabled again. To remove the apache2 startup scripts do the following:
To remove apache2 simply type:
sudo update-rc.d -f apache2 remove
Doing this will cause all runlevel folders that are linked to apache2 to be removed.
edited Feb 4 '18 at 13:46
MDijkstra
32
answered Aug 1 '12 at 2:47
tomodachitomodachi
9,70242343
Under the folder /etc/init.d/ you will find all the init scripts for different boot up services, like apache2, networking, etc.
Depending on which runlevel the computer starts in, different services are started.
So from the /etc/init.d/ folder each "service" is linked to one/many/no run level folders named from rc0.d to rc6.d.
To keep things simple there is a tool for removing/adding these links, hence removing or adding scripts to and from start up.
To disable apache2 simply type:
sudo update-rc.d apache2 disable
This disables apache2 at startup but is not removed so it can be enabled again. To remove the apache2 startup scripts do the following:
To remove apache2 simply type:
sudo update-rc.d -f apache2 remove
Doing this will cause all runlevel folders that are linked to apache2 to be removed.
edited Feb 4 '18 at 13:46
MDijkstra
32
answered Aug 1 '12 at 2:47
tomodachitomodachi
9,70242343
edited Feb 4 '18 at 13:46
MDijkstra
32
edited Feb 4 '18 at 13:46
MDijkstra
32
edited Feb 4 '18 at 13:46
MDijkstra
32
32
answered Aug 1 '12 at 2:47
tomodachitomodachi
9,70242343
answered Aug 1 '12 at 2:47
tomodachitomodachi
9,70242343
answered Aug 1 '12 at 2:47
tomodachitomodachi
9,70242343
9,70242343
2
chkconfig may also help - " chkconfig {service_name} off "
– MCR
Aug 1 '12 at 7:10
Doesn't work anymore:The script you are attempting to invoke has been converted to an Upstart job, but lsb-header is not supported for Upstart jobs. (...)
– TomDogg
Apr 29 '15 at 9:34
2
@TomDogg, can you specify the versions you were working with? This answer works for Apache 2 on Ubuntu 14.04.3
– Dale Anderson
Nov 2 '15 at 20:20
1
How to restore the service?
– Eugen Konkov
Apr 14 '16 at 8:12
9
Warning! This will REMOVE the service! Usesudo update-rc.d apache2 disable.
– Eduardo Cuomo
Jan 17 '17 at 19:37
|
show 2 more comments
2
chkconfig may also help - " chkconfig {service_name} off "
– MCR
Aug 1 '12 at 7:10
Doesn't work anymore:The script you are attempting to invoke has been converted to an Upstart job, but lsb-header is not supported for Upstart jobs. (...)
– TomDogg
Apr 29 '15 at 9:34
2
@TomDogg, can you specify the versions you were working with? This answer works for Apache 2 on Ubuntu 14.04.3
– Dale Anderson
Nov 2 '15 at 20:20
1
How to restore the service?
– Eugen Konkov
Apr 14 '16 at 8:12
9
Warning! This will REMOVE the service! Usesudo update-rc.d apache2 disable.
– Eduardo Cuomo
Jan 17 '17 at 19:37
2
2
chkconfig may also help - " chkconfig {service_name} off "
– MCR
Aug 1 '12 at 7:10
chkconfig may also help - " chkconfig {service_name} off "
– MCR
Aug 1 '12 at 7:10
Doesn't work anymore:
The script you are attempting to invoke has been converted to an Upstart job, but lsb-header is not supported for Upstart jobs. (...)– TomDogg
Apr 29 '15 at 9:34
Doesn't work anymore:
The script you are attempting to invoke has been converted to an Upstart job, but lsb-header is not supported for Upstart jobs. (...)– TomDogg
Apr 29 '15 at 9:34
2
2
@TomDogg, can you specify the versions you were working with? This answer works for Apache 2 on Ubuntu 14.04.3
– Dale Anderson
Nov 2 '15 at 20:20
@TomDogg, can you specify the versions you were working with? This answer works for Apache 2 on Ubuntu 14.04.3
– Dale Anderson
Nov 2 '15 at 20:20
1
1
How to restore the service?
– Eugen Konkov
Apr 14 '16 at 8:12
How to restore the service?
– Eugen Konkov
Apr 14 '16 at 8:12
9
9
Warning! This will REMOVE the service! Use
sudo update-rc.d apache2 disable.– Eduardo Cuomo
Jan 17 '17 at 19:37
Warning! This will REMOVE the service! Use
sudo update-rc.d apache2 disable.– Eduardo Cuomo
Jan 17 '17 at 19:37
|
show 2 more comments
you could simply disable it by:
sudo update-rc.d apache2 disable
and then if you would like to enable it again:
sudo update-rc.d apache2 enable
depending on the project i am working on, it is handy to have the service conveniently available, if i wish to re-enable it.
edited Dec 10 '14 at 18:47
tomodachi
9,70242343
answered Oct 8 '13 at 0:08
gsullinsgsullins
2,009173
4
enablegave me an error likerunlevel arguments (none) do not match LSB Default-Start values, butsudo update-rc.d apache2 defaultsappears to have re-enabled it successfully.
– here
Jan 13 '14 at 3:58
2
@heresudo update-rc.d apache2 enableplayed as expected for me
– Georgios Pligoropoulos
Feb 9 '14 at 15:12
1
On Ubuntu Trusty it tells me "The disable|enable API is not stable and might change in the future."
– Tanner
Jun 10 '14 at 0:31
1
Doesn't work -error: no runlevel symlinks to modify, aborting!. However, apache2 is running and autostarts.
– Daniel Kmak
Dec 14 '14 at 11:05
Doesn't work anymore:update-rc.d: error: no runlevel symlinks to modify, aborting!
– TomDogg
Apr 29 '15 at 9:33
|
show 5 more comments
you could simply disable it by:
sudo update-rc.d apache2 disable
and then if you would like to enable it again:
sudo update-rc.d apache2 enable
depending on the project i am working on, it is handy to have the service conveniently available, if i wish to re-enable it.
edited Dec 10 '14 at 18:47
tomodachi
9,70242343
answered Oct 8 '13 at 0:08
gsullinsgsullins
2,009173
4
enablegave me an error likerunlevel arguments (none) do not match LSB Default-Start values, butsudo update-rc.d apache2 defaultsappears to have re-enabled it successfully.
– here
Jan 13 '14 at 3:58
2
@heresudo update-rc.d apache2 enableplayed as expected for me
– Georgios Pligoropoulos
Feb 9 '14 at 15:12
1
On Ubuntu Trusty it tells me "The disable|enable API is not stable and might change in the future."
– Tanner
Jun 10 '14 at 0:31
1
Doesn't work -error: no runlevel symlinks to modify, aborting!. However, apache2 is running and autostarts.
– Daniel Kmak
Dec 14 '14 at 11:05
Doesn't work anymore:update-rc.d: error: no runlevel symlinks to modify, aborting!
– TomDogg
Apr 29 '15 at 9:33
|
show 5 more comments
you could simply disable it by:
sudo update-rc.d apache2 disable
and then if you would like to enable it again:
sudo update-rc.d apache2 enable
depending on the project i am working on, it is handy to have the service conveniently available, if i wish to re-enable it.
edited Dec 10 '14 at 18:47
tomodachi
9,70242343
answered Oct 8 '13 at 0:08
gsullinsgsullins
2,009173
you could simply disable it by:
sudo update-rc.d apache2 disable
and then if you would like to enable it again:
sudo update-rc.d apache2 enable
depending on the project i am working on, it is handy to have the service conveniently available, if i wish to re-enable it.
edited Dec 10 '14 at 18:47
tomodachi
9,70242343
answered Oct 8 '13 at 0:08
gsullinsgsullins
2,009173
edited Dec 10 '14 at 18:47
tomodachi
9,70242343
edited Dec 10 '14 at 18:47
tomodachi
9,70242343
edited Dec 10 '14 at 18:47
tomodachi
9,70242343
9,70242343
answered Oct 8 '13 at 0:08
gsullinsgsullins
2,009173
answered Oct 8 '13 at 0:08
gsullinsgsullins
2,009173
answered Oct 8 '13 at 0:08
gsullinsgsullins
2,009173
2,009173
4
enablegave me an error likerunlevel arguments (none) do not match LSB Default-Start values, butsudo update-rc.d apache2 defaultsappears to have re-enabled it successfully.
– here
Jan 13 '14 at 3:58
2
@heresudo update-rc.d apache2 enableplayed as expected for me
– Georgios Pligoropoulos
Feb 9 '14 at 15:12
1
On Ubuntu Trusty it tells me "The disable|enable API is not stable and might change in the future."
– Tanner
Jun 10 '14 at 0:31
1
Doesn't work -error: no runlevel symlinks to modify, aborting!. However, apache2 is running and autostarts.
– Daniel Kmak
Dec 14 '14 at 11:05
Doesn't work anymore:update-rc.d: error: no runlevel symlinks to modify, aborting!
– TomDogg
Apr 29 '15 at 9:33
|
show 5 more comments
4
enablegave me an error likerunlevel arguments (none) do not match LSB Default-Start values, butsudo update-rc.d apache2 defaultsappears to have re-enabled it successfully.
– here
Jan 13 '14 at 3:58
2
@heresudo update-rc.d apache2 enableplayed as expected for me
– Georgios Pligoropoulos
Feb 9 '14 at 15:12
1
On Ubuntu Trusty it tells me "The disable|enable API is not stable and might change in the future."
– Tanner
Jun 10 '14 at 0:31
1
Doesn't work -error: no runlevel symlinks to modify, aborting!. However, apache2 is running and autostarts.
– Daniel Kmak
Dec 14 '14 at 11:05
Doesn't work anymore:update-rc.d: error: no runlevel symlinks to modify, aborting!
– TomDogg
Apr 29 '15 at 9:33
4
4
enable gave me an error like runlevel arguments (none) do not match LSB Default-Start values, but sudo update-rc.d apache2 defaults appears to have re-enabled it successfully.– here
Jan 13 '14 at 3:58
enable gave me an error like runlevel arguments (none) do not match LSB Default-Start values, but sudo update-rc.d apache2 defaults appears to have re-enabled it successfully.– here
Jan 13 '14 at 3:58
2
2
@here
sudo update-rc.d apache2 enable played as expected for me– Georgios Pligoropoulos
Feb 9 '14 at 15:12
@here
sudo update-rc.d apache2 enable played as expected for me– Georgios Pligoropoulos
Feb 9 '14 at 15:12
1
1
On Ubuntu Trusty it tells me "The disable|enable API is not stable and might change in the future."
– Tanner
Jun 10 '14 at 0:31
On Ubuntu Trusty it tells me "The disable|enable API is not stable and might change in the future."
– Tanner
Jun 10 '14 at 0:31
1
1
Doesn't work -
error: no runlevel symlinks to modify, aborting!. However, apache2 is running and autostarts.– Daniel Kmak
Dec 14 '14 at 11:05
Doesn't work -
error: no runlevel symlinks to modify, aborting!. However, apache2 is running and autostarts.– Daniel Kmak
Dec 14 '14 at 11:05
Doesn't work anymore:
update-rc.d: error: no runlevel symlinks to modify, aborting!– TomDogg
Apr 29 '15 at 9:33
Doesn't work anymore:
update-rc.d: error: no runlevel symlinks to modify, aborting!– TomDogg
Apr 29 '15 at 9:33
|
show 5 more comments
With systemd we can now use systemctl commands to prevent a service from automatically starting at boot.
here is an example:
sudo systemctl disable apache2
You will still be able to start and stop the service but it won't start up at boot.
answered Sep 18 '15 at 22:20
mchidmchid
23.7k25287
2
Linux Mint is still based on Ubuntu 14.04. Ubuntu starts using systemd from 15.04 on.
– twan163
Dec 6 '15 at 23:01
1
@dragonmnl as twan163 said, systemd is for the newer versions (debian jessie or equivalent +)
– mchid
Dec 8 '15 at 21:55
1
this worked great on Debian
– Anupam
Jul 19 '17 at 12:37
1
the right answer for debian 9+
– John
Nov 24 '17 at 5:12
1
If encounterupdate-rc.d: error: no runlevel symlinks to modify, aborting!, recreate any below missing simlinks; then retry: /etc/rc0.d/K01<service> /etc/rc1.d/K01<service> /etc/rc2.d/S99<service> /etc/rc3.d/S99<service> /etc/rc4.d/S99<service> /etc/rc5.d/S99<service> /etc/rc6.d/K01<service>
– Amil Waduwawara
Aug 11 '18 at 2:26
|
show 3 more comments
With systemd we can now use systemctl commands to prevent a service from automatically starting at boot.
here is an example:
sudo systemctl disable apache2
You will still be able to start and stop the service but it won't start up at boot.
answered Sep 18 '15 at 22:20
mchidmchid
23.7k25287
2
Linux Mint is still based on Ubuntu 14.04. Ubuntu starts using systemd from 15.04 on.
– twan163
Dec 6 '15 at 23:01
1
@dragonmnl as twan163 said, systemd is for the newer versions (debian jessie or equivalent +)
– mchid
Dec 8 '15 at 21:55
1
this worked great on Debian
– Anupam
Jul 19 '17 at 12:37
1
the right answer for debian 9+
– John
Nov 24 '17 at 5:12
1
If encounterupdate-rc.d: error: no runlevel symlinks to modify, aborting!, recreate any below missing simlinks; then retry: /etc/rc0.d/K01<service> /etc/rc1.d/K01<service> /etc/rc2.d/S99<service> /etc/rc3.d/S99<service> /etc/rc4.d/S99<service> /etc/rc5.d/S99<service> /etc/rc6.d/K01<service>
– Amil Waduwawara
Aug 11 '18 at 2:26
|
show 3 more comments
With systemd we can now use systemctl commands to prevent a service from automatically starting at boot.
here is an example:
sudo systemctl disable apache2
You will still be able to start and stop the service but it won't start up at boot.
answered Sep 18 '15 at 22:20
mchidmchid
23.7k25287
With systemd we can now use systemctl commands to prevent a service from automatically starting at boot.
here is an example:
sudo systemctl disable apache2
You will still be able to start and stop the service but it won't start up at boot.
answered Sep 18 '15 at 22:20
mchidmchid
23.7k25287
answered Sep 18 '15 at 22:20
mchidmchid
23.7k25287
answered Sep 18 '15 at 22:20
mchidmchid
23.7k25287
answered Sep 18 '15 at 22:20
mchidmchid
23.7k25287
23.7k25287
2
Linux Mint is still based on Ubuntu 14.04. Ubuntu starts using systemd from 15.04 on.
– twan163
Dec 6 '15 at 23:01
1
@dragonmnl as twan163 said, systemd is for the newer versions (debian jessie or equivalent +)
– mchid
Dec 8 '15 at 21:55
1
this worked great on Debian
– Anupam
Jul 19 '17 at 12:37
1
the right answer for debian 9+
– John
Nov 24 '17 at 5:12
1
If encounterupdate-rc.d: error: no runlevel symlinks to modify, aborting!, recreate any below missing simlinks; then retry: /etc/rc0.d/K01<service> /etc/rc1.d/K01<service> /etc/rc2.d/S99<service> /etc/rc3.d/S99<service> /etc/rc4.d/S99<service> /etc/rc5.d/S99<service> /etc/rc6.d/K01<service>
– Amil Waduwawara
Aug 11 '18 at 2:26
|
show 3 more comments
2
Linux Mint is still based on Ubuntu 14.04. Ubuntu starts using systemd from 15.04 on.
– twan163
Dec 6 '15 at 23:01
1
@dragonmnl as twan163 said, systemd is for the newer versions (debian jessie or equivalent +)
– mchid
Dec 8 '15 at 21:55
1
this worked great on Debian
– Anupam
Jul 19 '17 at 12:37
1
the right answer for debian 9+
– John
Nov 24 '17 at 5:12
1
If encounterupdate-rc.d: error: no runlevel symlinks to modify, aborting!, recreate any below missing simlinks; then retry: /etc/rc0.d/K01<service> /etc/rc1.d/K01<service> /etc/rc2.d/S99<service> /etc/rc3.d/S99<service> /etc/rc4.d/S99<service> /etc/rc5.d/S99<service> /etc/rc6.d/K01<service>
– Amil Waduwawara
Aug 11 '18 at 2:26
2
2
Linux Mint is still based on Ubuntu 14.04. Ubuntu starts using systemd from 15.04 on.
– twan163
Dec 6 '15 at 23:01
Linux Mint is still based on Ubuntu 14.04. Ubuntu starts using systemd from 15.04 on.
– twan163
Dec 6 '15 at 23:01
1
1
@dragonmnl as twan163 said, systemd is for the newer versions (debian jessie or equivalent +)
– mchid
Dec 8 '15 at 21:55
@dragonmnl as twan163 said, systemd is for the newer versions (debian jessie or equivalent +)
– mchid
Dec 8 '15 at 21:55
1
1
this worked great on Debian
– Anupam
Jul 19 '17 at 12:37
this worked great on Debian
– Anupam
Jul 19 '17 at 12:37
1
1
the right answer for debian 9+
– John
Nov 24 '17 at 5:12
the right answer for debian 9+
– John
Nov 24 '17 at 5:12
1
1
If encounter
update-rc.d: error: no runlevel symlinks to modify, aborting!, recreate any below missing simlinks; then retry: /etc/rc0.d/K01<service> /etc/rc1.d/K01<service> /etc/rc2.d/S99<service> /etc/rc3.d/S99<service> /etc/rc4.d/S99<service> /etc/rc5.d/S99<service> /etc/rc6.d/K01<service>– Amil Waduwawara
Aug 11 '18 at 2:26
If encounter
update-rc.d: error: no runlevel symlinks to modify, aborting!, recreate any below missing simlinks; then retry: /etc/rc0.d/K01<service> /etc/rc1.d/K01<service> /etc/rc2.d/S99<service> /etc/rc3.d/S99<service> /etc/rc4.d/S99<service> /etc/rc5.d/S99<service> /etc/rc6.d/K01<service>– Amil Waduwawara
Aug 11 '18 at 2:26
|
show 3 more comments
Thought I'd just add to the answers by @gsullins and @tomodachi, for future readers who used the accepted answer.
If you've already used:
sudo update-rc.d apache2 remove
You can use the argument defaults to add apache2 back into the autostart
sudo update-rc.d apache2 defaults
Then you're able to enable/disable
sudo update-rc.d apache2 disable
sudo update-rc.d apache2 enable
answered Mar 1 '17 at 0:10
Ben WindingBen Winding
37329
add a comment |
Thought I'd just add to the answers by @gsullins and @tomodachi, for future readers who used the accepted answer.
If you've already used:
sudo update-rc.d apache2 remove
You can use the argument defaults to add apache2 back into the autostart
sudo update-rc.d apache2 defaults
Then you're able to enable/disable
sudo update-rc.d apache2 disable
sudo update-rc.d apache2 enable
answered Mar 1 '17 at 0:10
Ben WindingBen Winding
37329
add a comment |
Thought I'd just add to the answers by @gsullins and @tomodachi, for future readers who used the accepted answer.
If you've already used:
sudo update-rc.d apache2 remove
You can use the argument defaults to add apache2 back into the autostart
sudo update-rc.d apache2 defaults
Then you're able to enable/disable
sudo update-rc.d apache2 disable
sudo update-rc.d apache2 enable
answered Mar 1 '17 at 0:10
Ben WindingBen Winding
37329
Thought I'd just add to the answers by @gsullins and @tomodachi, for future readers who used the accepted answer.
If you've already used:
sudo update-rc.d apache2 remove
You can use the argument defaults to add apache2 back into the autostart
sudo update-rc.d apache2 defaults
Then you're able to enable/disable
sudo update-rc.d apache2 disable
sudo update-rc.d apache2 enable
answered Mar 1 '17 at 0:10
Ben WindingBen Winding
37329
answered Mar 1 '17 at 0:10
Ben WindingBen Winding
37329
answered Mar 1 '17 at 0:10
Ben WindingBen Winding
37329
answered Mar 1 '17 at 0:10
Ben WindingBen Winding
37329
37329
add a comment |
add a comment |
protected by Byte Commander Mar 3 '16 at 12:27
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
1
Perhaps someone can be more specific, but I can point you in the right direction... in /etc, there are directories for rc*.d, which contain all the start/stop scripts, called, I think, init scripts. You'll see links to scripts that are in /etc/init.d, and starting with either "k" or "s", for "kill" or "start", and a number which is the ordering.
– Marty Fried
Aug 1 '12 at 2:27
Yes, I knew about the /etc/rcX.d directories, but I searched for it to find out about some nicer tool, than just manually renaming files (life is too short).
update-rc.dhas filled this void.– Tomasz Gandor
Sep 26 '14 at 8:53