I have never been bothered by its existence. I might have used it once or twice but not recently.
I don't know what we gain by removing it. A few bytes of memory, and some extra magic that makes some special address ranges not appear in the interface list.
I think I would prefer to have all IPs and use filter(). There is WORKDIR/inputs/ignore_interfaces.rx that you could also use, kind of hard to find in the docs, just a small mention in the hard class documentation. https://docs.cfengine.com/latest/reference-classes.html#hard-classes
Anyone have a suggestion where it should be documented? I was looking for it in common control.
Anyway, I'd leave it given the choice, I prefer the more complete information.
--
You received this message because you are subscribed to the Google Groups "help-cfengine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to help-cfengin...@googlegroups.com.
To post to this group, send email to help-c...@googlegroups.com.
Visit this group at http://groups.google.com/group/help-cfengine.
For more options, visit https://groups.google.com/d/optout.
Is it not odd to have this in inputs? For me this makes it pretty useless as I purge everything in there in update_policy and as all most of my hosts have differing network setups so I can't manage this file? I'd like to exclude some bonds as the cfengine reports often come from private addresses in the subject. Guess I could template it... Somewhere like state would be a more suitable location for me?
Thoughts?
[1] in trainings, I had a Mac OS X laptop running VirtualBox hang for
several minutes while cf-agent was discovering that some bridged address
was invalid. Every time it ran.