New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
service resource misbehaves on upstart hosts #226
Comments
Hi @zmalone We used initctl due to the fact that Ubuntu recommends it http://upstart.ubuntu.com/cookbook/#initctl Will double-check why this does not work with Ubuntu 14.04. Any special configuration? |
It's unfortunately a default config. I believe this is just Ubuntu being inconsistent, but it happens with a few Ubuntu services, so checking init.d and the service command is probably necessary. This is a base Ubuntu 14.04 install:
|
Problem confirmed. This happens to all services located in |
#228 appears to fix this. Thank you! |
Some services, like ntp, don't show up in initctl on Ubuntu 14.04 and other pre-systemd platforms. They are visible in /etc/init.d and via the service command, but are not in initctl.
Currently, inspec checks initctl for all service resources on pre-15.04 hosts, so it will fail to detect running ntp processes, even though they are present and enabled.
I'm not sure what the proper fix here is, possibly checking /etc/init.d/, service, and initctl for a service, and or-ing the results together?
The text was updated successfully, but these errors were encountered: