On Fri, Apr 15, 2011 at 02:12:00PM -0400, Ted Zlatanov wrote:
>On Tue, 12 Apr 2011 08:13:29 -0500 Ted Zlatanov <t...@lifelogs.com> wrote:
>
>TZ> On Mon, 11 Apr 2011 15:26:19 -0500 Ted Zlatanov <t...@lifelogs.com> wrote:
>TZ> Actually it would be really nice if cfengine produced the list of
>TZ> interfaces in addition to the current net_iface_* classes.  It's already
>TZ> traversing the list of interfaces and providing sys.ipv4 so collecting
>TZ> their names in a sys.interfaces slist would be useful.
>
>TZ> I think it would be useful information to know the network driver, maybe
>TZ> as the mapped value if the key is the interface name.
>
>TZ> getindices("sys.ipv4") won't work with Infiniband interfaces, for
>TZ> instance (they can be sometimes configured with IPv4 addresses but it's
>TZ> not standard or reliable), and probably won't work with IPv6 according
>TZ> to the docs.  So knowledge of the driver would really help there,
>TZ> instead of relying on the interface name to match some regex as we do now.
>
>TZ> I think the right place to put this information is in sysinfo.c, see
>TZ> attached patch.  I don't know (yet) how to get the driver name from the
>TZ> ifreq structure.  Before I dive into the code and produce a full patch,
>TZ> can one of the cfengine maintainers please tell me if I'm on the right
>TZ> track and if this feature will be considered for inclusion?  If not I
>TZ> can just do it with a module in our environment.
>
>Does no one else need the true list of interfaces in cfengine?  I find
>that surprising.

I *could*, but don't yet.  If it existed, I'd use it.


-- 
Jesse Becker
NHGRI Linux support (Digicon Contractor)
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine

Reply via email to