Well, I don't think it's a special case as there are other services that have the option ENABLED in /etc/default. If a user launches services- admin to see if a service is started or not and the real things are different than what services-admin lists, I think we have a bug (we are disorienting the user).
What I think it's that the ENABLED options in /etc/default are redundants. In fact if I want a service to start or not I should only have to manipulate /etc/rc[0-6S].d and not, for particular services (that I don't know prior), enable or disable also the field ENABLED in the corresponding files in /etc/default. This redundancy brings to this issue. So for me, at last, services-admin may runs ok. -- services-admin says that a service is started but its /etc/default/ file has enabled = 0 https://bugs.launchpad.net/bugs/337988 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
