Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

This question is about finding a GUI or ncurses or whatever services manager for a Debian desktop. Something like this:

Mac example

Services manager on Windows

Windows example

Services manager on Mac

The ideas what it should do

The thing should be able to manage anything 'sudo service start/stop' handles, including

  • mysql
  • network-manager
  • networking
  • gdm, xdm
  • apache2

And it should

  • show description for each service
  • let me set the startup type (whether it starts on-boot automatically or I have to start it manually)

The ideas what it should not do

  • Not be rc.d. I would be somewhat interested in ways which don't involve reading what rc.d is.
  • Not be bum. I tried it.
    • names of some services are replaced with gibberish (Bum doesn't start for me anymore so I don't have a way to demo this problem; providing with a generic screenshot)
    • they don't have descriptions, and
    • there is no way to change the manual or automatic start-up type (i.e. tell mysql to stop starting onboot) BUM

OpenSUSE example

OpenSUSE example

share|improve this question

1 Answer 1

up vote 2 down vote accepted

Here are some that I know of. I am not sure what you mean about avoiding rc.d though.

  1. sysv-rc-conf

    enter image description here

    The numbers on the service row refer to runlevels.

  2. systemadm, installable on debian with sudo apt-get install systemd-gui:

    enter image description here

  3. Gnome services manager, services-admin, this may be what you refer to as bum but I am not sure.

    enter image description here

  4. A Perl script I found posted on a forum. It probably needs some tweaking (read the forum post) but could serve as a good starting point for you to play around with.

    enter image description here

share|improve this answer
    
1) I don't need to edit runlevels of a service. Only to tell it whether to start onboot or not. So if I set it to not boot, I will have to remember what runlevels it had to enable it again. However there is only one runlevel which would make sense for a certain service. Editing it is not needed. Remembering is hard and redundant. 2) There is no systemd-admin package on Ubuntu. 3) Does set a service to [not] start on boot. 3) Per the script, "As of now, there is no actual functionality, it just scans the services; Makes a GUI and when the Apply button is pressed prints what would be done." –  user89272 Mar 15 '13 at 21:32
    
@Gryllida 1) Editing the runlevels of a service is how you tell it to start at boot or not, look up runlevels. You do not need to remember, you just need to understand what runlevels are and how they work. The runlevel you are interested in is probably 5. Those services with 5 checked "start on boot". 2) What is systemd-admin? I said systemd-gui. 3) I said it could serve as a starting point. As I said, read the forum post. 4) You'd think a simple "thank you for your time" might have fit somewhere in your last comment. –  terdon Mar 17 '13 at 13:27
    
Thank you for your time! (the comment length was quite limiting, I had 0 chars left! ;-) A) systemd-gui isn't found in the repos either..... B) the runlevels stuff is, wouldn't it be up to a packager to tell the runlevel, so i simply tell whether to trigger the run or not? –  user89272 Mar 20 '13 at 10:07
    
Packager is the person who packages something (i.e. packages mysql). /They/ know what runlevel it belongs to. I should have an option of not caring and just using the default runlevel, right? –  user89272 Mar 24 '13 at 11:30
    
No, it is not up to them. The package will be set up with its default settings. Mysql, for example will start on boot by default. It is then up to the susadmin to tweak as desired. –  terdon Mar 24 '13 at 11:32

Your Answer

 
discard

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