Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

One of my applications is at a infinite loop in the runlevel 1 by printing No protocol specified continuously after running startx -- :1. The run level does not listen to my commands given at the run level. I can of course give kernel Magic*B, but that would close all my other run levels which I do not want. Magic*K is not working.

One nasty way of stopping the run level is by removing components such as /etc/rc1.d/*.*bluetooth.*. However, I do not see this a good way in the long run.

How can you kill all processes at the run level 1 which belongs to the open prompt in the given run level?

share|improve this question

migrated from Dec 8 '09 at 22:45

This question came from our site for professional and enthusiast programmers.

I think you'll have better luck at – Jonathan Feinberg Dec 4 '09 at 21:05
your use of the term "runlevel" is confusing. the system is only in a single runlevel at a time. could you please clarify? maybe give the steps you're using to arrive at the problem state. like this: "1. boot into runlevel 1; 2. run startx -- :1 ; 3. can't kill -9 it and nothing works!" – quack quixote Dec 23 '09 at 8:37
up vote 3 down vote accepted

A clean way to do this would be to use update-rc.d. You can configure the program to not run at all during runlevel 1:

$update-rc.d script_name stop 1 .

where script_name is the init.d script. So for example, to stop Apache from running in runlevel 1:

$update-rc.d apache2 stop 1 .

If you want to completely disable the specified service:

$update-rc.d -f script_name remove

If you are going to disable a service, you should also stop it from running in all runlevels. Next time a service is upgraded, the init.d scripts may be recreated, essentially re-enabling your service.

To disable it in all runlevels:

$update-rc.d script_name stop 80 0 1 2 3 4 5 6 .
share|improve this answer
I get the following warnings – Masi Dec 21 '09 at 13:20
Oh, apache was just an example! what program is giving you the errors? Is it bluetooth or another application? – John T Dec 22 '09 at 0:20

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.