On Tue, Jan 12, 2010 at 2:49 PM, Dan Bode <d...@reductivelabs.com> wrote:
> > > On Tue, Jan 12, 2010 at 1:12 AM, Jesús Couto <jesus.co...@gmail.com>wrote: > >> >> >>> the start and stop params take a command, not a file. (just like status) >>> You are executing the filename as a command, which will return 1. >>> >>> >> No, thats the idea, to execute them. Those last files are scripts to start >> & stop the instances. I also thought the solution you mention, to create the >> init.d scripts so I use a service with, say, the debian provider. But I >> fixed the problem, now it executes the scripts and starts the services. >> Doesnt stop them but that seems to be something else :-( >> >> > can you share the contents of the init script? does it have a #!/bin/bash > statement? can you try executing with bash > > its this ERB template #!/bin/bash . /etc/webinstances/<%= name %>/envvars /usr/sbin/apache2 -f /etc/webinstances/<%= name %>/apache2.conf -k start As you see, very simple. And now it works cause the apache2 line was having output, that was what was making it not run. I'm not sure why the stop script is not being invoked when I say ensure => stopped - I think it has to do with not finding the status line on the ps listing? What would be the advantage of running it by calling bash? ------------------------------ Jesús Couto F.--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet-us...@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.
