Unrecognised escape sequences
mt321_0987
puppet masters:
" [...] Unrecognised escape sequence '\<CHAR>' in file <PATH> [...] "
but then everything works fine; also, without using escapes, catalogs
dont work on agents.
What can we do to avoid these kind of errors in master syslogs?
Please ,let us know ASAP and tell us if this problem will prevent
remote execution in future versions, thanks
Greets,
Matteo
Felix Frank
If you have strings that include backslashes, you should really escape
those backslashes, i.e.:
onlyif => "grep two\ words /tmp/file", # WRONG!
onlyif => "grep two\\ words /tmp/file", # right
In some cases, you can use single quotes instead
onlyif => 'grep two\ words /tmp/file', # right too
but you loose flexibility. I urge you to get your escapes right.
HTH,
Felix
M C
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..
Please help,
greets,
Matteo
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Felix Frank
> 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
M C
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
Felix
Felix Frank
> Hi,
>
> 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>' [...] "
The above line is giving you this warning? Please make double-sure.
There are lot of cases where this warning is justified, but the above
line should *not* generate it, as all of those sequences should be
recognized.
M C
thank you verymuch.
Matteo
--