On Jan 27, 2011 4:58 AM, "Johan Sunnerstig" <johan.sunners...@auriga.se> wrote: > > > ...because a whole bunch of init scripts on Debian didn't provide a > > functional 'status' method, which meant that puppet would fail in a > > whole other exciting way. :( > > So I guess the best way to solve it on my end would be to simply specify hasstatus and such per service I guess?
Uh-huh. If the status argument to init scripts becomes more robustly available we might look to being smarter, but for now you need to check that and tell puppet. Sorry. > > We already have a bug report about this, and the problem is that we > > can't just tell users of stable to stick with older version of puppet > > – so the Debian provider needs to support both r5 and r6, which means > > detecting the availability of the 'disable' option and using it when > > possible. > > > > Given we are under some release pressure at the moment ourselves you > > can move this along by providing concrete information about how we can > > determine if 'disable' is supported, ideally without mistaking "failed > > to disable" for "can't disable". > > > Patches also happily accepted, of course. :) > > Aside from being a pretty horrible programmer, I also know next to nothing about Ruby. :) Well, I figure it never hurts to ask. :) Regards, Daniel -- Puppet Labs Developer –http://puppetlabs.com Daniel Pittman <dan...@puppetlabs.com> Contact me via gtalk, email, or phone: +1 (877) 575-9775 Sent from a mobile device. Please forgive me if this is briefer than usual. -- 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.