Mark,
First off, thanks for the quick reply.
On Fri, Jun 13, 2008 at 15:31, Mark Burgess <[EMAIL PROTECTED]> wrote:
>
> Will,
>
> I don't really have time to look closely right now, but this might be due to
> a bug that was cleared up a while ago. You could try 2.2.7 to see if it
> works.
Thanks for the suggestion. It does seem that 2.2.1 was (part of) the
problem, the other problem being that I reordered the "inputs" section
of cfagent.conf and moved the group definitions into the middle of the
file instead of being the first thing. The other problem I ran into
(and am still running into) is the treatment of colons in strings.
With 2.2.7, it complained about a lot of lines with colons in the
shell scripts, e.g.:
shellcommands:
"/usr/sbin/svcadm enable svc:/network/security/ktkt_warn:default"
needed \es added before the colons before cfagent would accept it.
However, some other things apparently did not treat colons the same
way; changing : out for \: in
editfiles:
{ /etc/shadow
ReplaceLineWith "root\:$(password_hash)\:13627\:0\:99999\:7\:\:\:"
}
put \:s all over our /etc/shadow.
So, the question arises: how are colons really treated in
double-quoted strings? Are they treated differently in regexes as
opposed to double-quoted strings? Is there a simpler way to get the
old "treat colons as colons not separators" behavior everywhere?
Thanks!
Will
_______________________________________________
Bug-cfengine mailing list
[email protected]
https://cfengine.org/mailman/listinfo/bug-cfengine
