On Wed, 20 Apr 2005, Pip Oomen wrote:
>
> IMHO, this is a bug then, since resolv.conf syntax requires the colon for
> options. The fix would be to either not allow for list expansion in the
> resolve action, or to define ${colon} to work around the issue.
here's that patch to add ${colon} wil mentioned, maybe it'll help.
--
- Eric Sorenson - N37 17.255 W121 55.738 - http://eric.explosive.net -
- Personal colo with a professional touch - http://www.explosive.net -Index: cf.defs.h
===================================================================
--- cf.defs.h (revision 46)
+++ cf.defs.h (working copy)
@@ -879,6 +879,7 @@
cfcr,
cfn,
cfdblquote,
+ cfcolon,
cfquote,
cfdollar,
cfrepchar,
Index: varstring.c
===================================================================
--- varstring.c (revision 46)
+++ varstring.c (working copy)
@@ -79,6 +79,7 @@
"cr",
"n",
"dblquote",
+ "colon",
"quote",
"dollar",
"repchar",
@@ -695,6 +696,15 @@
}
strcat(buffer,"\'");
break;
+
+ case cfcolon:
+ if (ExpandOverflow(buffer," "))
+ {
+ FatalError("Can't expandvarstring");
+ }
+ strcat(buffer,":");
+ break;
+
case cfdollar:
_______________________________________________
Bug-cfengine mailing list
Bug-cfengine@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-cfengine
