I'll try and find the bug in a second, but apparently the lack of any return codes from /etc/init.d/foo status when a service has been upstarted is a bug.
Ultimately I feel puppet needs an initctl based service provider.
I'll try and find the bug in a second, but apparently the lack of any return codes from /etc/init.d/foo status when a service has been upstarted is a bug.
Ultimately I feel puppet needs an initctl based service provider.