Issue #883 has been updated by Luke Kanies. Assigned to deleted (Luke Kanies) Target version changed from unplanned to Statler
---------------------------------------- Bug #883: Puppet configuration run time calculation not 'internal' http://projects.puppetlabs.com/issues/883 Author: Joshua Timberman Status: Accepted Priority: Low Assigned to: Category: unknown Target version: Statler Patch: None Affected version: 0.25.4 Keywords: Branch: I'm not sure how to summarize clearly, so I will expound here. From puppetd --test: notice: Finished configuration run in 18252.08 seconds It took less than a minute to run, probably. We just updated our config with an NTP module now that the NTP server is online. Right after I logged in: $ date Mon Oct 29 17:03:58 UTC 2007 $ puppetd --test [...] notice: //basenode/ntp/Service[ntpd]/ensure: ensure changed 'stopped' to 'running' [...] notice: Finished configuration run in 18252.08 seconds $ date Mon Oct 29 22:08:36 UTC 2007 It looks like puppet checks the timestamp of the system before it runs, and then again afterward to calculate the run time, rather than timing everything internally? -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- 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.
