Issue #21770 has been updated by eric sorenson. Status changed from Unreviewed to Code Insufficient Target version changed from 3.3.0 to 3.x Branch set to https://github.com/puppetlabs/puppet/pull/1769
Updated branch info it's easy to find the code. But it looks like the PR is in limbo; at any rate I'm bumping the release version out from 3.3.0 since that ship is sailing. ---------------------------------------- Feature #21770: Add SIGINFO support to Puppet on systems that have this signal https://projects.puppetlabs.com/issues/21770#change-96579 * Author: Will Farrington * Status: Code Insufficient * Priority: Normal * Assignee: * Category: * Target version: 3.x * Affected Puppet version: * Keywords: * Branch: https://github.com/puppetlabs/puppet/pull/1769 ---------------------------------------- If the user sends SIGINFO to the Puppet process during the evaluation of a resource, Puppet will generate an INFO level message with the type and title of the resource currently being applied. Below is an example of what this looks like in practice. Please note I've added whitespace for emphasis, and in use none of these empty lines are present. ``` ~ $ puppet apply -e ' exec { ["/bin/sleep 20", "/bin/sleep 10"]: } ' load: 1.50 cmd: ruby 86469 running 1.59u 0.29s Evaluating resource: exec[/bin/sleep 10] Notice: /Stage[main]//Exec[/bin/sleep 10]/returns: executed successfully load: 1.46 cmd: ruby 86469 running 1.59u 0.30s Evaluating resource: exec[/bin/sleep 20] Notice: /Stage[main]//Exec[/bin/sleep 20]/returns: executed successfully Notice: Finished catalog run in 30.10 seconds ``` This functionality is geared at users who may not be running Puppet in debug mode when they encounter slow resource application times. While strace/dtrace can provide context into what resource is currently being applied, that's not terribly user-friendly. SIGINFO allows users to, on supported systems, simply invoke `<Control>-T` during resource application to yield any long-running resource apply phases. SIGINFO is typically a BSD and BSD-derivative platform signal. This change does not introduce breakages for non-BSD, POSIX systems; nor does it introduce breakages for the Windows platform. -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
