Rudder

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. :)