[Puppet Users] Re: Issue with service = disabled and stopped

2012-11-26 Thread jcbollinger
On Tuesday, November 20, 2012 6:11:17 PM UTC-6, Forrie wrote: Thanks, I went ahead and added an exit 1 at the bottom of each of these scripts to shut it up. That's probably not quite right, but maybe it will work well enough for you. At least, in the case of the cups-

[Puppet Users] Re: Issue with service = disabled and stopped

2012-11-20 Thread jcbollinger
On Monday, November 19, 2012 6:37:28 PM UTC-6, Forrie 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

[Puppet Users] Re: Issue with service = disabled and stopped

2012-11-20 Thread Forrie
Thanks, I went ahead and added an exit 1 at the bottom of each of these scripts to shut it up. At least, in the case of the cups- config-daemon, it's been deprecated so I can just remove that check. HIDD is another issue. Most of the init.d scripts use RETVAL=$? after the status) query -- so

[Puppet Users] Re: Issue with service = disabled and stopped

2012-11-19 Thread Forrie
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

Re: [Puppet Users] Re: Issue with service = disabled and stopped

2012-11-19 Thread Matthaus Owens
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.