I see, thanks. Not sure how I got it to work before with use=service, unless maybe the service module's auto-detection method changed since 2.2. Anyway, I guess I can work around it with "command" for now, until there's a sysv module available.
On Thursday, December 14, 2017 at 10:54:47 AM UTC-8, Brian Coca wrote: > > The use parameter is still valid, it lets you override the selection, > but the 'use=service' defaults to the 'old ansible service module' , > which still does it's own autodetection and uses systemd if present > (it always did). > > It does NOT use the 'service' command, which varies by distro/OS and > has diff implementations, though the service plugin can use it, it is > not what the `use` parameter does. > > > > -- > ---------- > Brian Coca > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/1fb352e8-65b0-43ea-8851-2a8f770c72b3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
