Stop program running at startup in Linux
How do I stop a program running at startup in Linux. I want to remove some apps from startup to allow them to be managed by supervisord
e.g apache2
linux startup shutdown boot
add a comment |
How do I stop a program running at startup in Linux. I want to remove some apps from startup to allow them to be managed by supervisord
e.g apache2
linux startup shutdown boot
That's exactly why I didn't tag it... I'm looking for all the variations as I work with quite a few different distros.
– Frozenskys
Aug 10 '10 at 21:15
add a comment |
How do I stop a program running at startup in Linux. I want to remove some apps from startup to allow them to be managed by supervisord
e.g apache2
linux startup shutdown boot
How do I stop a program running at startup in Linux. I want to remove some apps from startup to allow them to be managed by supervisord
e.g apache2
linux startup shutdown boot
linux startup shutdown boot
edited Apr 28 '13 at 19:42
Anthon
61.2k17104168
61.2k17104168
asked Aug 10 '10 at 19:41
FrozenskysFrozenskys
4372712
4372712
That's exactly why I didn't tag it... I'm looking for all the variations as I work with quite a few different distros.
– Frozenskys
Aug 10 '10 at 21:15
add a comment |
That's exactly why I didn't tag it... I'm looking for all the variations as I work with quite a few different distros.
– Frozenskys
Aug 10 '10 at 21:15
That's exactly why I didn't tag it... I'm looking for all the variations as I work with quite a few different distros.
– Frozenskys
Aug 10 '10 at 21:15
That's exactly why I didn't tag it... I'm looking for all the variations as I work with quite a few different distros.
– Frozenskys
Aug 10 '10 at 21:15
add a comment |
7 Answers
7
active
oldest
votes
Depending on your distro use the chkconfig or update-rc.d tool to enable/disable system services.
On a redhat/suse/mandrake style system:
sudo chkconfig apache2 off
On Debian:
sudo update-rc.d -f apache2 remove
Checkout their man pages for more info.
Why do you need -f (I assume it's force) on Debian based distros?
– Frozenskys
Aug 10 '10 at 20:05
2
There are two sets of files in play here. You've got the actual init script in /etc/init.d/ and you have the links to it in your runlevel directory /etc/rcrunlevel.d/. These guys point to the script in /etc/init.d/ If you don't use -f update-rd.d will fail UNLESS the script in /etc/init.d/ is already deleted. If you do use -f update-rc.d will properly delete the link files regardless of whether or not the /etc/init.d/ script is deleted.
– jacksonh
Aug 10 '10 at 20:38
Ah, that makes a lot of sense, I'd forgotten that the runlevel scripts were just links to the init scripts. Thanks for the extra explanation.
– Frozenskys
Aug 10 '10 at 21:18
add a comment |
If you are dealing with a modern Ubuntu system and a few other distros you may have to deal with a combination of traditional init scripts and upstart scripts. Managing init scripts is covered by other answers. The following is one way to stop an upstart service from starting on boot:
# mv /etc/init/servicename.conf /etc/init/servicename.conf.disabled
The problem with this method is that it does not allow you to start the service using:
# service start servicename
An alternative to this is to open the servicename.conf
file in your favorite editor and comment out any lines that start with:
start on
That is, change this to
#start on ...
where the "..." is whatever was after "start on" previously. This way, when you want to re-enable it, you don't have to remember what the "start on" parameters were.
Finally, if you have a new version of upstart you can simply add the word "manual" to the end of the configuration file. You can do this directly from the shell:
# echo "manual" >> /etc/init/servicename.conf
This will cause upstart to ignore any "start on" phrases earlier in the file.
add a comment |
On recent Fedora and Future RHEL systems
systemctl disable httpd.service
will disable the httpd service
add a comment |
Slackware and Arch linux have similar methods of stopping/starting processes at boot, different than the Ubuntu and Redhat-style examples given above.
In both Slackware and Arch linuxes, sh scripts exist in directory /etc/rc.d
, typically one script per daemon, or one script per subsystem.
For example, Slackware starts the Apache web server with a script /etc/rc.d/rc.httpd
, called at the appropriate time during system startup with an argument of "start". Arch linux has differently-named scripts, but the same sort of thing goes on.
To keep some process from starting during system boot, on Slackware, you just make the appropriate script in /etc/rc.d not executable. To keep Apache from starting at the next boot:
chmod -x /etc/rc.d/rc.httpd
To stop an Apache that got started at boot: /etc/rc.d/rc.httpd stop
You'll need to be root.
Arch is a bit more complex. The file /etc/rc.conf, a shell script, has an array DAEMONS. To keep Apache from starting at boot, you'd change 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 an already executing apache, you'd execute /etc/rc.d/httpd stop
as root.
add a comment |
On Ubuntu 10.04 you can control some startup programs from the GUI.
System→Preferences→Startup Applications
1
Original image is no longer there.
– Tshepang
Mar 3 '11 at 21:28
add a comment |
To list all the startup services
systemctl
To stop a service from running on start up
sudo systemctl disable servicename
For instance if we need to stop running ssh server at startup
sudo systemctl disable sshd.service
We can enable this again using
sudo systemctl enable sshd.service
Almost every linux distributions use systemd for bootstrapping startup services. So above commands work for most of the distros.
New contributor
add a comment |
1) tap superkey on you keyboard
2) search for 'Startup Applications'
3) choose which program you want to disable
4) hit like to this answer if worx.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f13%2fstop-program-running-at-startup-in-linux%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
7 Answers
7
active
oldest
votes
7 Answers
7
active
oldest
votes
active
oldest
votes
active
oldest
votes
Depending on your distro use the chkconfig or update-rc.d tool to enable/disable system services.
On a redhat/suse/mandrake style system:
sudo chkconfig apache2 off
On Debian:
sudo update-rc.d -f apache2 remove
Checkout their man pages for more info.
Why do you need -f (I assume it's force) on Debian based distros?
– Frozenskys
Aug 10 '10 at 20:05
2
There are two sets of files in play here. You've got the actual init script in /etc/init.d/ and you have the links to it in your runlevel directory /etc/rcrunlevel.d/. These guys point to the script in /etc/init.d/ If you don't use -f update-rd.d will fail UNLESS the script in /etc/init.d/ is already deleted. If you do use -f update-rc.d will properly delete the link files regardless of whether or not the /etc/init.d/ script is deleted.
– jacksonh
Aug 10 '10 at 20:38
Ah, that makes a lot of sense, I'd forgotten that the runlevel scripts were just links to the init scripts. Thanks for the extra explanation.
– Frozenskys
Aug 10 '10 at 21:18
add a comment |
Depending on your distro use the chkconfig or update-rc.d tool to enable/disable system services.
On a redhat/suse/mandrake style system:
sudo chkconfig apache2 off
On Debian:
sudo update-rc.d -f apache2 remove
Checkout their man pages for more info.
Why do you need -f (I assume it's force) on Debian based distros?
– Frozenskys
Aug 10 '10 at 20:05
2
There are two sets of files in play here. You've got the actual init script in /etc/init.d/ and you have the links to it in your runlevel directory /etc/rcrunlevel.d/. These guys point to the script in /etc/init.d/ If you don't use -f update-rd.d will fail UNLESS the script in /etc/init.d/ is already deleted. If you do use -f update-rc.d will properly delete the link files regardless of whether or not the /etc/init.d/ script is deleted.
– jacksonh
Aug 10 '10 at 20:38
Ah, that makes a lot of sense, I'd forgotten that the runlevel scripts were just links to the init scripts. Thanks for the extra explanation.
– Frozenskys
Aug 10 '10 at 21:18
add a comment |
Depending on your distro use the chkconfig or update-rc.d tool to enable/disable system services.
On a redhat/suse/mandrake style system:
sudo chkconfig apache2 off
On Debian:
sudo update-rc.d -f apache2 remove
Checkout their man pages for more info.
Depending on your distro use the chkconfig or update-rc.d tool to enable/disable system services.
On a redhat/suse/mandrake style system:
sudo chkconfig apache2 off
On Debian:
sudo update-rc.d -f apache2 remove
Checkout their man pages for more info.
answered Aug 10 '10 at 19:46
jacksonhjacksonh
3,02611513
3,02611513
Why do you need -f (I assume it's force) on Debian based distros?
– Frozenskys
Aug 10 '10 at 20:05
2
There are two sets of files in play here. You've got the actual init script in /etc/init.d/ and you have the links to it in your runlevel directory /etc/rcrunlevel.d/. These guys point to the script in /etc/init.d/ If you don't use -f update-rd.d will fail UNLESS the script in /etc/init.d/ is already deleted. If you do use -f update-rc.d will properly delete the link files regardless of whether or not the /etc/init.d/ script is deleted.
– jacksonh
Aug 10 '10 at 20:38
Ah, that makes a lot of sense, I'd forgotten that the runlevel scripts were just links to the init scripts. Thanks for the extra explanation.
– Frozenskys
Aug 10 '10 at 21:18
add a comment |
Why do you need -f (I assume it's force) on Debian based distros?
– Frozenskys
Aug 10 '10 at 20:05
2
There are two sets of files in play here. You've got the actual init script in /etc/init.d/ and you have the links to it in your runlevel directory /etc/rcrunlevel.d/. These guys point to the script in /etc/init.d/ If you don't use -f update-rd.d will fail UNLESS the script in /etc/init.d/ is already deleted. If you do use -f update-rc.d will properly delete the link files regardless of whether or not the /etc/init.d/ script is deleted.
– jacksonh
Aug 10 '10 at 20:38
Ah, that makes a lot of sense, I'd forgotten that the runlevel scripts were just links to the init scripts. Thanks for the extra explanation.
– Frozenskys
Aug 10 '10 at 21:18
Why do you need -f (I assume it's force) on Debian based distros?
– Frozenskys
Aug 10 '10 at 20:05
Why do you need -f (I assume it's force) on Debian based distros?
– Frozenskys
Aug 10 '10 at 20:05
2
2
There are two sets of files in play here. You've got the actual init script in /etc/init.d/ and you have the links to it in your runlevel directory /etc/rcrunlevel.d/. These guys point to the script in /etc/init.d/ If you don't use -f update-rd.d will fail UNLESS the script in /etc/init.d/ is already deleted. If you do use -f update-rc.d will properly delete the link files regardless of whether or not the /etc/init.d/ script is deleted.
– jacksonh
Aug 10 '10 at 20:38
There are two sets of files in play here. You've got the actual init script in /etc/init.d/ and you have the links to it in your runlevel directory /etc/rcrunlevel.d/. These guys point to the script in /etc/init.d/ If you don't use -f update-rd.d will fail UNLESS the script in /etc/init.d/ is already deleted. If you do use -f update-rc.d will properly delete the link files regardless of whether or not the /etc/init.d/ script is deleted.
– jacksonh
Aug 10 '10 at 20:38
Ah, that makes a lot of sense, I'd forgotten that the runlevel scripts were just links to the init scripts. Thanks for the extra explanation.
– Frozenskys
Aug 10 '10 at 21:18
Ah, that makes a lot of sense, I'd forgotten that the runlevel scripts were just links to the init scripts. Thanks for the extra explanation.
– Frozenskys
Aug 10 '10 at 21:18
add a comment |
If you are dealing with a modern Ubuntu system and a few other distros you may have to deal with a combination of traditional init scripts and upstart scripts. Managing init scripts is covered by other answers. The following is one way to stop an upstart service from starting on boot:
# mv /etc/init/servicename.conf /etc/init/servicename.conf.disabled
The problem with this method is that it does not allow you to start the service using:
# service start servicename
An alternative to this is to open the servicename.conf
file in your favorite editor and comment out any lines that start with:
start on
That is, change this to
#start on ...
where the "..." is whatever was after "start on" previously. This way, when you want to re-enable it, you don't have to remember what the "start on" parameters were.
Finally, if you have a new version of upstart you can simply add the word "manual" to the end of the configuration file. You can do this directly from the shell:
# echo "manual" >> /etc/init/servicename.conf
This will cause upstart to ignore any "start on" phrases earlier in the file.
add a comment |
If you are dealing with a modern Ubuntu system and a few other distros you may have to deal with a combination of traditional init scripts and upstart scripts. Managing init scripts is covered by other answers. The following is one way to stop an upstart service from starting on boot:
# mv /etc/init/servicename.conf /etc/init/servicename.conf.disabled
The problem with this method is that it does not allow you to start the service using:
# service start servicename
An alternative to this is to open the servicename.conf
file in your favorite editor and comment out any lines that start with:
start on
That is, change this to
#start on ...
where the "..." is whatever was after "start on" previously. This way, when you want to re-enable it, you don't have to remember what the "start on" parameters were.
Finally, if you have a new version of upstart you can simply add the word "manual" to the end of the configuration file. You can do this directly from the shell:
# echo "manual" >> /etc/init/servicename.conf
This will cause upstart to ignore any "start on" phrases earlier in the file.
add a comment |
If you are dealing with a modern Ubuntu system and a few other distros you may have to deal with a combination of traditional init scripts and upstart scripts. Managing init scripts is covered by other answers. The following is one way to stop an upstart service from starting on boot:
# mv /etc/init/servicename.conf /etc/init/servicename.conf.disabled
The problem with this method is that it does not allow you to start the service using:
# service start servicename
An alternative to this is to open the servicename.conf
file in your favorite editor and comment out any lines that start with:
start on
That is, change this to
#start on ...
where the "..." is whatever was after "start on" previously. This way, when you want to re-enable it, you don't have to remember what the "start on" parameters were.
Finally, if you have a new version of upstart you can simply add the word "manual" to the end of the configuration file. You can do this directly from the shell:
# echo "manual" >> /etc/init/servicename.conf
This will cause upstart to ignore any "start on" phrases earlier in the file.
If you are dealing with a modern Ubuntu system and a few other distros you may have to deal with a combination of traditional init scripts and upstart scripts. Managing init scripts is covered by other answers. The following is one way to stop an upstart service from starting on boot:
# mv /etc/init/servicename.conf /etc/init/servicename.conf.disabled
The problem with this method is that it does not allow you to start the service using:
# service start servicename
An alternative to this is to open the servicename.conf
file in your favorite editor and comment out any lines that start with:
start on
That is, change this to
#start on ...
where the "..." is whatever was after "start on" previously. This way, when you want to re-enable it, you don't have to remember what the "start on" parameters were.
Finally, if you have a new version of upstart you can simply add the word "manual" to the end of the configuration file. You can do this directly from the shell:
# echo "manual" >> /etc/init/servicename.conf
This will cause upstart to ignore any "start on" phrases earlier in the file.
edited Mar 7 '11 at 23:39
answered Mar 7 '11 at 23:24
Steven DSteven D
32.7k898108
32.7k898108
add a comment |
add a comment |
On recent Fedora and Future RHEL systems
systemctl disable httpd.service
will disable the httpd service
add a comment |
On recent Fedora and Future RHEL systems
systemctl disable httpd.service
will disable the httpd service
add a comment |
On recent Fedora and Future RHEL systems
systemctl disable httpd.service
will disable the httpd service
On recent Fedora and Future RHEL systems
systemctl disable httpd.service
will disable the httpd service
answered Apr 29 '13 at 2:12
AlastairAlastair
111
111
add a comment |
add a comment |
Slackware and Arch linux have similar methods of stopping/starting processes at boot, different than the Ubuntu and Redhat-style examples given above.
In both Slackware and Arch linuxes, sh scripts exist in directory /etc/rc.d
, typically one script per daemon, or one script per subsystem.
For example, Slackware starts the Apache web server with a script /etc/rc.d/rc.httpd
, called at the appropriate time during system startup with an argument of "start". Arch linux has differently-named scripts, but the same sort of thing goes on.
To keep some process from starting during system boot, on Slackware, you just make the appropriate script in /etc/rc.d not executable. To keep Apache from starting at the next boot:
chmod -x /etc/rc.d/rc.httpd
To stop an Apache that got started at boot: /etc/rc.d/rc.httpd stop
You'll need to be root.
Arch is a bit more complex. The file /etc/rc.conf, a shell script, has an array DAEMONS. To keep Apache from starting at boot, you'd change 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 an already executing apache, you'd execute /etc/rc.d/httpd stop
as root.
add a comment |
Slackware and Arch linux have similar methods of stopping/starting processes at boot, different than the Ubuntu and Redhat-style examples given above.
In both Slackware and Arch linuxes, sh scripts exist in directory /etc/rc.d
, typically one script per daemon, or one script per subsystem.
For example, Slackware starts the Apache web server with a script /etc/rc.d/rc.httpd
, called at the appropriate time during system startup with an argument of "start". Arch linux has differently-named scripts, but the same sort of thing goes on.
To keep some process from starting during system boot, on Slackware, you just make the appropriate script in /etc/rc.d not executable. To keep Apache from starting at the next boot:
chmod -x /etc/rc.d/rc.httpd
To stop an Apache that got started at boot: /etc/rc.d/rc.httpd stop
You'll need to be root.
Arch is a bit more complex. The file /etc/rc.conf, a shell script, has an array DAEMONS. To keep Apache from starting at boot, you'd change 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 an already executing apache, you'd execute /etc/rc.d/httpd stop
as root.
add a comment |
Slackware and Arch linux have similar methods of stopping/starting processes at boot, different than the Ubuntu and Redhat-style examples given above.
In both Slackware and Arch linuxes, sh scripts exist in directory /etc/rc.d
, typically one script per daemon, or one script per subsystem.
For example, Slackware starts the Apache web server with a script /etc/rc.d/rc.httpd
, called at the appropriate time during system startup with an argument of "start". Arch linux has differently-named scripts, but the same sort of thing goes on.
To keep some process from starting during system boot, on Slackware, you just make the appropriate script in /etc/rc.d not executable. To keep Apache from starting at the next boot:
chmod -x /etc/rc.d/rc.httpd
To stop an Apache that got started at boot: /etc/rc.d/rc.httpd stop
You'll need to be root.
Arch is a bit more complex. The file /etc/rc.conf, a shell script, has an array DAEMONS. To keep Apache from starting at boot, you'd change 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 an already executing apache, you'd execute /etc/rc.d/httpd stop
as root.
Slackware and Arch linux have similar methods of stopping/starting processes at boot, different than the Ubuntu and Redhat-style examples given above.
In both Slackware and Arch linuxes, sh scripts exist in directory /etc/rc.d
, typically one script per daemon, or one script per subsystem.
For example, Slackware starts the Apache web server with a script /etc/rc.d/rc.httpd
, called at the appropriate time during system startup with an argument of "start". Arch linux has differently-named scripts, but the same sort of thing goes on.
To keep some process from starting during system boot, on Slackware, you just make the appropriate script in /etc/rc.d not executable. To keep Apache from starting at the next boot:
chmod -x /etc/rc.d/rc.httpd
To stop an Apache that got started at boot: /etc/rc.d/rc.httpd stop
You'll need to be root.
Arch is a bit more complex. The file /etc/rc.conf, a shell script, has an array DAEMONS. To keep Apache from starting at boot, you'd change 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 an already executing apache, you'd execute /etc/rc.d/httpd stop
as root.
answered Mar 7 '11 at 21:37
Bruce EdigerBruce Ediger
35.4k667120
35.4k667120
add a comment |
add a comment |
On Ubuntu 10.04 you can control some startup programs from the GUI.
System→Preferences→Startup Applications
1
Original image is no longer there.
– Tshepang
Mar 3 '11 at 21:28
add a comment |
On Ubuntu 10.04 you can control some startup programs from the GUI.
System→Preferences→Startup Applications
1
Original image is no longer there.
– Tshepang
Mar 3 '11 at 21:28
add a comment |
On Ubuntu 10.04 you can control some startup programs from the GUI.
System→Preferences→Startup Applications
On Ubuntu 10.04 you can control some startup programs from the GUI.
System→Preferences→Startup Applications
edited May 28 '15 at 9:19
Spooky
20126
20126
answered Aug 12 '10 at 16:36
jjclarksonjjclarkson
1,32711315
1,32711315
1
Original image is no longer there.
– Tshepang
Mar 3 '11 at 21:28
add a comment |
1
Original image is no longer there.
– Tshepang
Mar 3 '11 at 21:28
1
1
Original image is no longer there.
– Tshepang
Mar 3 '11 at 21:28
Original image is no longer there.
– Tshepang
Mar 3 '11 at 21:28
add a comment |
To list all the startup services
systemctl
To stop a service from running on start up
sudo systemctl disable servicename
For instance if we need to stop running ssh server at startup
sudo systemctl disable sshd.service
We can enable this again using
sudo systemctl enable sshd.service
Almost every linux distributions use systemd for bootstrapping startup services. So above commands work for most of the distros.
New contributor
add a comment |
To list all the startup services
systemctl
To stop a service from running on start up
sudo systemctl disable servicename
For instance if we need to stop running ssh server at startup
sudo systemctl disable sshd.service
We can enable this again using
sudo systemctl enable sshd.service
Almost every linux distributions use systemd for bootstrapping startup services. So above commands work for most of the distros.
New contributor
add a comment |
To list all the startup services
systemctl
To stop a service from running on start up
sudo systemctl disable servicename
For instance if we need to stop running ssh server at startup
sudo systemctl disable sshd.service
We can enable this again using
sudo systemctl enable sshd.service
Almost every linux distributions use systemd for bootstrapping startup services. So above commands work for most of the distros.
New contributor
To list all the startup services
systemctl
To stop a service from running on start up
sudo systemctl disable servicename
For instance if we need to stop running ssh server at startup
sudo systemctl disable sshd.service
We can enable this again using
sudo systemctl enable sshd.service
Almost every linux distributions use systemd for bootstrapping startup services. So above commands work for most of the distros.
New contributor
New contributor
answered 25 mins ago
PrincePrince
1
1
New contributor
New contributor
add a comment |
add a comment |
1) tap superkey on you keyboard
2) search for 'Startup Applications'
3) choose which program you want to disable
4) hit like to this answer if worx.
add a comment |
1) tap superkey on you keyboard
2) search for 'Startup Applications'
3) choose which program you want to disable
4) hit like to this answer if worx.
add a comment |
1) tap superkey on you keyboard
2) search for 'Startup Applications'
3) choose which program you want to disable
4) hit like to this answer if worx.
1) tap superkey on you keyboard
2) search for 'Startup Applications'
3) choose which program you want to disable
4) hit like to this answer if worx.
answered Sep 24 '16 at 9:00
Bhasha BhavanishankarBhasha Bhavanishankar
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f13%2fstop-program-running-at-startup-in-linux%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
That's exactly why I didn't tag it... I'm looking for all the variations as I work with quite a few different distros.
– Frozenskys
Aug 10 '10 at 21:15