On Nov 11, 10:13 am, Arnau Bria <arnaub...@pic.es> wrote:
> I'm just trying to control a service that does not run a process but
> enables a cron (like yum autoupdate or pakiti).
What Bellman said. Puppet is limited in what it can do for you if
your initscipt's status command doesn't return an accurate status.
If you have a broken initscript and you can't fix it / get it fixed,
then there are alternatives:
1) Live with the error. Puppet will try to "start" the service every
time it runs. If afterward it double-checks that the service is
running (I'm uncertain whether it does) then it will report an error.
As long as nothing else has a declared dependency on the Service then
such an error can probably be ignored.
2) You may be able to configure the Service so that Puppet doesn't
manage whether or not it's running. Try leaving out the "ensure"
parameter, and if that doesn't work then try setting it to undef
(ensure => undef). The idea is that Puppet will manage the links in /
etc/rc*.d/, but it won't try to start (or stop) the service.
With that said, it would be far better to use a correct initscript .
John
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
