Greetings, Shouldn''t puppetd -o --ignoreschedules ... imply that splay* options are ignored :-) If that''s not the intended behavior could we get a --run-now that ignores splay* and schedules? Cheers, Ryan
On Oct 17, 2007, at 12:00 PM, Ryan Dooley wrote:> Shouldn''t puppetd -o --ignoreschedules ... imply that splay* > options are > ignored :-) If that''s not the intended behavior could we get a -- > run-now > that ignores splay* and schedules?Hmm. This is one of the reasons I never liked splay -- it''s a pain for humans to deal with. --test adds --no-splay, and you''re running interactively, that''s what you should normally do. My guess is that if you run puppetd -t --ignoreschedules, you''ll get the behaviour you want. I''m not sure about adding an option that does -t and ignores schedules; what do others think? -- It''s impossible to foresee the consequences of being clever. -- Christopher Strachey --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
On 10/17/07 10:10 AM, "Luke Kanies" <luke@madstop.com> wrote: On Oct 17, 2007, at 12:00 PM, Ryan Dooley wrote:> Shouldn''t puppetd -o --ignoreschedules ... imply that splay* > options are > ignored :-) If that''s not the intended behavior could we get a -- > run-now > that ignores splay* and schedules?Hmm. This is one of the reasons I never liked splay -- it''s a pain for humans to deal with. --test adds --no-splay, and you''re running interactively, that''s what you should normally do. Groovy, I''ll try that here in a second. My guess is that if you run puppetd -t --ignoreschedules, you''ll get the behaviour you want. I''m not sure about adding an option that does -t and ignores schedules; what do others think? My thought here was for system installation. The first thing I do is to check for a host key in my ssl directory. If that doesn''t exist, I run puppet with -o to pull the initial configuration. I suppose the installed package (which provides puppet.conf) should just leave out the splay options. Once the first run is done, the current puppet.conf will be pulled from the local puppet master. That''s what I''ll do in the short term eagerly awaiting 0.23.3 :-) Cheers, Ryan _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
On Oct 17, 2007, at 12:35 PM, Ryan Dooley wrote:> My thought here was for system installation. The first thing I do > is to check for a host key in my ssl directory. If that doesn’t > exist, I run puppet with –o to pull the initial configuration. I > suppose the installed package (which provides puppet.conf) should > just leave out the splay options. Once the first run is done, the > current puppet.conf will be pulled from the local puppet master.Use --test (or -t), rather than -o; you''ll be much happier.> That’s what I’ll do in the short term eagerly awaiting 0.23.3 :-)Hrm, keep waiting. I''m not planning on putting out another point release; I''m hard at work on 0.24.0, which will have the REST work in it. I expect it to be a pretty disruptive release, but we''ll see. -- Those who speak most of progress measure it by quantity and not by quality. --George Santayana --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
> That''s what I''ll do in the short term eagerly awaiting 0.23.3 :-)Hrm, keep waiting. I''m not planning on putting out another point release; I''m hard at work on 0.24.0, which will have the REST work in it. I expect it to be a pretty disruptive release, but we''ll see. /me eagerly awaits (0.24.0) :-) _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users