Comment 14 for bug 435935

Hello Milan and thank you for working on this as it is very much needed. From what I understand (after reading this bug and testing the packages in your PPA) is that your services-admin completely ignores upstart jobs and allows a user to only enable/disable SysV scripts. Only my testing shows different results. I am not able to disable SysV scripts (such as the one which starts the ssh service), whereas rcconf does the job correctly.

I am also not able to disable GDM (to start the computer in command line) and UFW (to start the computer without a firewall). Both which have been converted to upstart (I believe; I mean they do have an upstart /etc/init/<serv>.conf file) and it is reasonable to expect that a user may need to turn them off (I know this goes against your theory of "Upstart jobs are hidden since they are the less interesting to disable").

After my tests I don't believe this is what was intended by the "Upstart compatible services-admin[1]" blueprint. First, we need a way to have a non-destructive means to disable an upstart job (as explained in Bug #94065 [2]). Currently, the way I use to disable an upstart job is to rename a config file for the service needed:

$ mv /etc/init/<serv>.conf /etc/init/<serv>.away

Once the non-destructive method of disabling a job has been introduced, services-admin will need to be changed to use that method. A that point, I would say that we are one step closer to making a services-admin that can handle the init -> upstart transition. Until then, headaches distinguishing jobs from scripts, renaming upstart .conf files, and using update-rc.d/rcconf for SysV scripts.

Meanwhile, do you have any idea why ssh doesn't show up in your services-admin? Did you create a filter list for the items that show up (or stay hidden) in services-admin?

[1] https://blueprints.launchpad.net/ubuntu/+spec/desktop-lucid-services-settings-window
[2] Bug #94065 (upstart) - init: add non-destructive means to disable a job