> Instead, one has to pay attention to which init system is active (I'm not sure what the "official" way is to do that, but we can find that out).
Right. Checking files is *never* correct, as both in upstart and in systemd you can always override them (e. g. /etc/init/*.override or a file in /etc/systemd/system/ or /run/systemd/system/ overrides a file in /lib/systemd/system). > Or perhaps puppet should exclusively be using the "service" wrapper now That is the correct thing to do. service works under SysV, upstart, and systemd. The only thing to keep in mind is that "service status foo" always exits with 0 under upstart even if a service isn't running. Arguably this really ought to be fixed, so if you need that functionality let's fix that properly instead of working around it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457957 Title: puppet uses upstart for service status checks in vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
