Both of these init scripts always return 0. Puppet assumes that the init script will return 0 as a status for a running service and nonzero for a stopped service. Because of this, when Puppet calls `service hidd status` to see if hidd needs to be stopped, it thinks it does, as status returns 0.
hidd ships with a deficient init script. It makes the right calls to start, stop, and get the status of the hidd service, but it never does anything with the returns from those calls so it always falls through to the bottom of the script where 0 is returned. On Mon, Nov 19, 2012 at 4:37 PM, Forrie <for...@gmail.com> wrote: > Thanks for the explanation, I appreciate it. > > These services are provided by Redhat as are the init scripts, which > report: > > > # /etc/init.d/cups-config-daemon status > cups-config-daemon is obsolete > > # /etc/init.d/hidd status > hidd is stopped > > > I can see where the first one is unexpected to Puppet. > > I am running: > > # puppet --version > 2.7.19 > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- Matthaus Owens Release Manager, Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
