I recall now that there is a chicken-egg problem with having this in the
policy file.
Having mulled over this for several months, I think the best approach is
to have a file
of regular expressions
inputs/ignore_interfaces.rx
that contains regular expressions to match interface names, e.g. eth.*
This is in trunk now.
M
On 03/01/2012 11:45 PM, Brian Bennett wrote:
I came across this old post on the mailing list:
https://cfengine.org/pipermail/help-cfengine/2009-December/006811.html
Quoting the relevant portion:
Mark Burgess wrote:
Ouch. Perhaps we can make a configuration setting to ignore interfaces.
Bryan Ramirez wrote:
Some of our servers have a large number of virtual interfaces
(between 300 and 1200). I'm finding that cf-agent can take anywhere
between 15 to 40 minutes to run on these hosts depending on how many
virtual interfaces are on the machine.
I have the same situation, where I have 250-500 addresses on
interfaces and things are going to get more complicated as we add IPv6
and potentially have 250-500 inet6 addresses as well.
In some of our tests (using cfengine2) we've overflowed the classes
buffer. So I'm wondering if this has been implemented yet. Does
anybody know?
--
Brian
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine
--
CTO and Founder
CFEngine
http://www.cfengine.com
http://www.markburgess.org
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine
