Andrew, the oddity that I ran into was strictly because I made the
mistake of trying to specify a value for splay. Luckily enough it was
on my puppet dev machines so I had to go in manually and modify 4
diferent server configs.
It is definitely one of those grey lined areas that needs some
Jason,
I agree, open an issue that explains the failure and what you consider the
desired behavior.
I'm not sure Puppet should just ignore and keep running, but it should at
least do something informative.
Andrew
On Fri, Jan 30, 2009 at 9:43 PM, Jason Rojas wrote:
>
> The one issue I have seen
The one issue I have seen with puppet managing itself is if someone
adds something stupid like:
"--splay=300"
To /etc/sysconfig/puppet "EXTRA_OPTS"
(yes I am speaking from experience)
Puppet will restart and die instead of ignoring and warning about the
bad configuration option.
This could b
On Jan 30, 8:04 am, Dan Bode wrote:
> Hi all,
>
> Is there a way to push out the puppet.conf file from puppet?
Puppet CAN update itself. It will restart when a new puppet.conf is
found.
Use the File type.
>
> If I change report = true in a manifest, then will the current run be
> reported?
I
