Hi, the problem we are facing is not the transfer of backslash escape+non-specific character; we need puppet not to log the warns into the syslog when catalogs are prepared and commands such as
command => "/bin/echo \"\$(echo bin)\"", are processed for compiling Our syslogs are full of " [...] Unrecognised escape sequence '\<non-specific character>' [...] " Please help, thanks Greets, Matteo 2011/2/9 Felix Frank <felix.fr...@alumni.tu-berlin.de> > On 02/09/2011 12:13 PM, M C wrote: > > Hi, > > > > it aint our issue: we dont actually need to include escape chars into > > strings, our need is - for example - to escape delimitators ( ", ' ) > > inside command lines; in fact ,we're used to compose very complex tiny > > scripts with subshells for the 'command' field into 'exec' resources, > etc.. > > My comment was not targeted at escaping specific characters. Whatever > you escape, if you want puppet to transfer a backslash to the client, > and the string containing that backslash is double-quoted in your > manifest, you should escape that backslash and avoid any ambiguity. > > Regards, > Felix > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.