there is also a param for service called "pattern" that allows you to
specify the regex that should be used to determine the process (in case one
of them doesnt properly implement status)
On Thu, Oct 15, 2009 at 8:53 PM, Matthias Saou <
th...@spam.spam.spam.spam.spam.spam.spam.egg.and.spam.freshrpms.net> wrote:
>
> Douglas Garstang <doug.garst...@gmail.com> wrote:
>
> [...]
> > It seems to me like there might be a bug here. Puppet appears to think
> > the syslog-ng and syslog service are the same thing and stops
> > syslog-ng instead of syslog.
> > If I change the name of the syslog service, like this...
> >
> > service { "XXXsyslog":
> > ensure => stopped,
> > enable => false;
> > }
> >
> > then puppet does NOT stop syslog-ng. Is it doing a regex search on the
> > first part of the service name or something and stopping when it gets
> > a match?
>
> I think puppet looks for the process name by default. What you want to
> do is use "hasstatus => true" after making sure that "service syslog
> status" returns a correct exit status (i.e. zero only when the service
> is actually running).
>
> Matthias
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
