The root issue is that the "service" resource only depends upon the
Package. You need to include all of the other resources in the require,
or chain the requires in such a way that all of the other work is done
before puppet tries to start apache. That will fix the "double run" issue.
Marc Zam
Hi,
Looks like you're over engineering a bit here. You are creating directories
that I think will be created by the package manager. You can obviously sets
perms on those directories but I would drop unnecessary creates.
Also you don't have any order in the structure. You need to include 'notif
Hey guys,
Thanks for your input!
I have yet to start paring down the execs as per your suggestion,
however I did implement your suggestion of using the absent attribute
as opposed to the Tidy resource type.
file { "/etc/httpd/conf.d/ssl.conf":
ensure => absent,
require
Hi,
May not be the best solution, but you could keep the ssl.conf file declaration
but it's source could be made harmless, ie, have a file called ssl.conf that
has the httpd directives hashed out.
That way the file can exist but not interfere.
There maybe better ways though.
Cheers,
On 16/
On 3/15/2011 6:40 PM, Tim Dunphy wrote:
hello list!!
I have developed a custom apache module for my company that setups up
our own particular config of httpd and php in order to run our sites..
However, there is one wrinkle. It take two puppet runs to start the
httpd service with this module a
hello list!!
I have developed a custom apache module for my company that setups up
our own particular config of httpd and php in order to run our sites..
However, there is one wrinkle. It take two puppet runs to start the
httpd service with this module and we'd like to get that down to one
run!
