Issue #2527 has been updated by Peter Meier.
> Note sure if I should re-open a bug or not: I'm now using 0.25.1, and this > feature still seems to be missing. well the bug is still open, it simply haven't yet been implemented. > I changed the puppetd.rb code in order to add a "--loglevel" option. > This option allow to change the loglevel registered at startup. It only > applies if no other option set the loglevel (i.e. --test). If the given > loglevel is not valid it uses the current default value (info). > As I'm not very familiar with ruby code, here is the patch (diff -u) for the > version I have. Please let me know if I should use an other way to submit > this. you can propose a patch on the dev-list. For more details have a look @ http://reductivelabs.com/trac/puppet/wiki/Development/DevelopmentLifecycle ---------------------------------------- Feature #2527: Cannot suppress notice messages from puppet http://projects.reductivelabs.com/issues/2527 Author: Anselm Strauss Status: Accepted Priority: Low Assigned to: Category: newfeature Target version: Affected version: 0.24.8 Keywords: Branch: There is no option to run puppet quietly, so it only shows errors and warnings, notices are always shown. Maybe a --quiet switch besides the --verbose and --debug switches would not be bad. Or even better a more sophisticated log level option for filtering arbitrary log level messages and combinations of different levels. -- 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://reductivelabs.com/redmine/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.
