Bug #4423
closed
systemd & upstart service management: The servicesManagement technique has no answer status for Service starting parameters on Ubuntu 12.04
Description
The servicesManagement technique has No Answer status for Service starting parameters on Ubuntu 12.04. It looks like the check method is not valid, since this is handled by Upstart nowadays. However, if I manually do an "update-rc.d [service] defaults", the status will become Success. Unfortunatly half of the services in Ubuntu have been moved to Upstart (/etc/init/[service].conf) and other services are still managed by sysvinit. I assume the same will happen with Red Hat nodes, as soon as Red Hat (partially) moves to systemd.
The only thing I can think of on how to solve this, is to add an dropdown where a user manually can define if the service is managed by sysvinit or Upstart. However, for now the default should be sysvinit. Just my 2 cents. :)
Updated by François ARMAND almost 11 years ago
- Subject changed from The servicesManagement technique has no answer status for Service starting parameters on Ubuntu 12.04 to systemd & upstart service management: The servicesManagement technique has no answer status for Service starting parameters on Ubuntu 12.04
That is a very good point. We must take that into account.
We could check based on distribution version, or perhaps there is a more generic way to find the deamon used - there is not so much to test for...
Updated by Benoît PECCATTE over 9 years ago
- Category set to Techniques
- Target version set to Ideas (not version specific)
Updated by Alexis Mousset almost 8 years ago
- Status changed from New to Rejected
This is fixed in #7192, and will be partially backported in older ncf branches. Closing.