On Mon, Jan 17, 2011 at 9:01 PM, Luke Kanies <[email protected]> wrote:
> On Jan 17, 2011, at 5:41 PM, Nigel Kersten wrote: > > > > On Sun, Jan 16, 2011 at 5:05 PM, James Turnbull > <[email protected]>wrote: > >> >> Signed-off-by: James Turnbull <[email protected]> >> --- >> lib/puppet/util/command_line/puppetd | 5 ----- >> 1 files changed, 0 insertions(+), 5 deletions(-) >> >> diff --git a/lib/puppet/util/command_line/puppetd >> b/lib/puppet/util/command_line/puppetd >> index cb8589c..0abee90 100755 >> --- a/lib/puppet/util/command_line/puppetd >> +++ b/lib/puppet/util/command_line/puppetd >> @@ -126,11 +126,6 @@ >> # Defaults to sending messages to syslog, or the console if debugging >> or >> # verbosity is enabled. >> # >> -# no-client:: >> -# Do not create a config client. This will cause the daemon to run >> -# without ever checking for its configuration automatically, and only >> -# makes sense when used in conjunction with --listen. >> -# >> # onetime:: >> # Run the configuration once. Runs a single (normally daemonized) >> Puppet run. >> # Useful for interactively running puppet agent when used in >> conjunction with >> -- >> 1.7.3.4 >> >> > Did we stop supporting this or did it never work? The ticket history isn't > particularly useful either... > > > It hasn't really been relevant since the 0.24 release cycle. There's no > longer a 'client' object any more. > > You could say it's analogous to the agent class, so I could see having that > option supported to not have the agent class, but.... I don't really see > why, and I doubt anyone ever used it. > > I'd rather remove that and move to simpler executables, rather than this > complicated agent class. > Sounds reasonable. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en.
