Issue #11860 has been updated by Stefan Schulte.
Just wanted to say that I also hit this bug today and we are not running ruby 1.9, just ruby 1.8.7: We used puppet to patch our monitoring software on ~200 systems. After puppet was done, monitoring events with german umlauts turned into garbage. We first blamed the vendor of our monitoring software of course but after some digging I found out that restarting the monitoring daemon with a clean environment cleared the mess. So as FJ Landzaat said: It is not only a language problem, it is an encoding problem. This freaked my out a little bit and made me thinking of potential impact in other areas (like installing a database that runs under a false locale unnoticed). #4695 states that it might break your postgres databases. If this is really true I think this is worth backporting to 2.7.x and 2.6.x actually. ---------------------------------------- Bug #11860: Puppet ovewriting the LANG environment variable. https://projects.puppetlabs.com/issues/11860#change-60550 Author: Marek Kroemeke Status: Merged - Pending Release Priority: Urgent Assignee: Chris Price Category: exec Target version: Telly Affected Puppet version: 2.7.0 Keywords: Branch: https://github.com/puppetlabs/puppet/pull/414 As far as I can see puppet is changing system's LANG environment variable - this causes unexpected bahaviour of applications that use this setting (as LANG is different when you run /etc/init.d/foo stop/start/restart, and different when service is restarted by puppet!). -- 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.
