Hi,
internationalization issues are likely as not caused by the underlying
Ruby runtime, rather than Puppet itself. Or so I guess. Are you running
a Ruby that came with your copy of Puppet? (Is this how Puppet works on
Windows?)
On 01/12/2016 06:39 PM, Matthieu Dubuget wrote:
I spent some days testing puppet on a clone of a real windows 2008 R2
file server.
While puppet seems very interesting, I’m afraid it is not mature
enough to be used with Windows clients?
The main problem is that the files served by my file server were
created by french people: their names contain lot of accentuated
characters.
First, I had to do |chcp 1252| before I could use puppet. The default
code page is 850. Not really friendly. But manageable.
Wait, code pages? Can Windows not be set to run everything in unicode?
(Excuse my ignorance, my patience for running Windows in production has
been limited so far.)
The second problem I’m facing now, appears while using simple
manifests like the following one:
|acl { 'd:/Data/Directory': permissions => ... } |
It works fine, and is faster than I would have expected, even when the
permissions are to be applied to a lot of files.
But as soon as there is any file whose path contain special character
(like |é| or |è|) in the target directory (|d:/Data/Directory|), the
puppet apply command fails.
Is there any solution to this problem, or should I forget puppet for
some time?
Thanks for any advice
How does it fail? Can you share the error message? Please also make a
run of puppet agent with an added --trace flag and share the full output
including stack traces.
Thanks,
Felix
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/56B76BD1.1010002%40Alumni.TU-Berlin.de.
For more options, visit https://groups.google.com/d/optout.
