#1100: client should not sleep for $splay_time when triggered by puppetrun
-----------------------------+----------------------------------------------
Reporter: alden | Owner: community
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: client | Version: 0.24.1
Severity: normal | Resolution:
Keywords: puppetrun splay | Stage: Needs more info
Patch: Code | Complexity: Easy
-----------------------------+----------------------------------------------
Comment (by RyanDooley):
Replying to [comment:2 luke]:
> The problem here is that he wants splat disabled on the client (the
machine he's connecting to), not the machine that's running puppetrun.
>
> He specifically wants some way for the client to know if it was
triggered with puppetrun rather than normally.
>
> The problem I have with this request is that sometimes people will
desire the current behaviour (so they can trigger many hosts at once) and
sometimes they will desire instant triggers.
Since I think I posted this a quick comment:
In our environment I have a tool that triggers behavior on many machines
and I taught it about puppet. The same tool has a splay feature built in
so I can control how quickly my clients check in.
Now, that's not for everybody and probably not even for me in the future
as the plant grows in size but it would still be nice to have this option.
--
Ticket URL: <http://reductivelabs.com/trac/puppet/ticket/1100#comment:4>
puppet <http://reductivelabs.com>
Puppet - Portable System Automation
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
