Yes.
I switched from using the 'resolve:' stuff (which never worked well for
me) to copying out a file. The file is being copied just fine, but
cfengine is also rebuilding the file despite "resolve" being commented
out in the actionsequence. The file is copied out earlier (in
update.conf) and the resolve section was in the main config file, so it
basically copies out a correct file then stomps on it with a bare-bones
dynamically generated resolver.
Commenting out the entire resolve: section seemed to get it to stop,
although I have only tested this a couple times as yet.
Martin, Jason H wrote:
Have you checked for a 'copy' statement that is maintaining resolv.conf
as well?
-Jason Martin
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Chip Seraphine
Sent: Wednesday, September 07, 2005 5:31 AM
To: Bug-Cfengine
Subject: Resolv.conf being maintained whether I like it or not
In 2.1.15 on Linux:
I'm finding that the resolv.conf is rebuilt even if the "resolve:"
action is *not* in the actionsequence. The expected behavior (as per
the Reference) would be that the resolve: stuff would be inert if not
triggered from actionsequence.
--
Chip Seraphine
Unix Administrator
TradeLink, LLC
312-264-2048
[EMAIL PROTECTED]
_______________________________________________
Bug-cfengine mailing list
Bug-cfengine@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-cfengine
