Issue #11044 has been updated by Brice Figureau.
R.I. Pienaar wrote: > I like this idea but would prefer the behavior to be configurable I think, it > will certain solve a lot of pain for many ppl Note that it doesn't fork for --onetime runs, like the ones out of cron. But, yes we can add a settings. ---------------------------------------- Feature #11044: Puppet agent should fork when applying the catalog https://projects.puppetlabs.com/issues/11044 Author: Brice Figureau Status: In Topic Branch Pending Review Priority: Normal Assignee: Brice Figureau Category: agent Target version: Affected Puppet version: Keywords: Branch: https://github.com/masterzen/puppet/tree/tickets/2.7.x/11044 The current best practice among Puppet users is to run the puppet agent out of cron with --onetime. The rationale is that the puppet agent is a memory hog during a run, but due to the way the ruby interpreter works this memory can never be returned to the OS between runs. Running on cron makes sure puppet doesn't hold this memory for more than the run. A simple solution to this issue is to fork into a child process and do the catalog run. This process would exit at the end of the catalog execution, thus freeing the memory used during the run. -- 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.
