Issue #4836 has been updated by Jonathan Kinred.
I regularly see this confusing new users. I'd like to see the time that Puppet was locked in the output. Less important, but what might also be nice is to allow time-based locking, like "lock for X minutes" or "lock until <time>". ---------------------------------------- Feature #4836: puppetd --disable improvements https://projects.puppetlabs.com/issues/4836 Author: micah - Status: Accepted Priority: Low Assignee: Category: error reporting Target version: Statler Affected version: 0.25.5 Keywords: Branch: Occasionally I disable regular puppetd runs on a system by doing: <pre> # puppetd --disable </pre> This works fine, except that it could be improved in two ways: 1. If it has been manually disabled, then when a run is attempted, it should print something more useful than this: <pre> notice: Run of Puppet configuration client already in progress; skipping </pre> because well... that message isn't really true, its not in progress, rather it is currently disabled. 2. The something more useful that it could print could be either a default message "notice: Puppet administratively disabled on this system; skipping", or a custom message that you can pass to the puppetd --disable, eg. "puppetd --disable micah is fixing stunnel template" would then print the following when a puppetd was running: "notice: Puppet is administratively disabled because micah is fixing stunnel template; skipping 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.
