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
consideration and input from others.
Considering the impact modifying puppet configs can have on all puppet
managed servers; I know falling back to last config state would be
difficult, but at least a warning and puppet ignoringthe entire config
option may be a better suited solution.
If I have a chance tomorrow I will jump on IRC or start a new thread
about this. (I'm trying not to hijack threads)
But if Luke or James or anyone else wants to chime in I am looking for
input on whether this is desired functionality for puppet.
-Jason
On Jan 30, 2009, at 11:47 PM, Andrew Shafer <and...@reductivelabs.com>
wrote:
> 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 <ja...@nothingbeatsaduck.com
> > wrote:
>
> 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 be a common mistake in general, and I think this would be a
> reasonible safety precaution.
>
> -Jason
>
> On Jan 30, 2009, at 5:31 AM, Larry Ludwig <larry...@gmail.com> wrote:
>
> >
> > On Jan 30, 8:04 am, Dan Bode <bod...@gmail.com> 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 believe it's after the current run it restarts.
> >
> >
> >> Also, I saw something interesting when I ran
> >>
> >> puppetd --genmanifest
> >>
> >> It has a class called
> >> class reporting {
> >> file { '/var/lib/puppet/reports':
> >> loglevel => 'debug',
> >> backup => 'false',
> >> owner => 'puppet',
> >> group => 'puppet',
> >> mode => '488',
> >> ensure => 'directory'
> >> }}
> >>
> >> (there are lots of other interesting things in this output as well)
> >>
> >> two questions related to this file.
> >>
> >> 1. Do I have access to all of these classes for puppet runs, can I
> >> set
> >> reporting per client in the manifests?
> >
> > per client via the puppet.conf file
> >
> >> 2. How does puppet know to execute all of these things before the
> >> manifests
> >> on the server? Does this imply that there is a way to run init
> >> tasks (before
> >> everything else) without creating tons of dependencies?
> >> (ex: configure yum-repos)
> > >
> >
>
>
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
