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..
Please
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'
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 [...]
On 02/09/2011 01:22 PM, M C wrote:
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
Hi,
thank you verymuch.
Matteo
2011/2/9 Felix Frank felix.fr...@alumni.tu-berlin.de
On 02/09/2011 01:22 PM, M C wrote:
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
On 02/08/2011 04:09 PM, mt321_0987 wrote:
unfortunately, we keep getting this warns into the system log by
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
