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 start => 'bash /tmp/command.sh' > > > >> You can specify the same resources on multiple nodes. >> >> Resources must be unique per compiled catalog. Only resources for a >> certain host will be compiled into its catalog. >> > > Hmmm... that clears it a lot, thanks! > > Best regards, > > -- > ------------------------------ > > 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<puppet-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >--
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.
