NetworkManager/system-settings/plugins/ifcfg-rh/nm-ifcfg-rh.xml
Dan Williams d0f5c92ed9 ifcfg-rh: provide an easy way to get connection UUID/path for tools
ifup/ifdown, nmcli, and possibly other tools need a way to get the
internally generated connection UUID and possibly it's path given
just the ifcfg file path.  Not all ifcfg files have the UUID in
the file, so ifcfg-rh generates one.  But external tools don't know
what that UUID is or what the logic that NM uses to generate it is.

Help them out a bit so that ifup/ifdown can easily poke NM given
just the ifcfg file.
2010-02-17 16:43:03 -08:00

31 lines
1.2 KiB
XML

<?xml version="1.0" encoding="UTF-8" ?>
<node name="/" xmlns:tp="http://telepathy.freedesktop.org/wiki/DbusSpec#extensions-v0">
<interface name="com.redhat.ifcfgrh1">
<tp:docstring>
Utility methods for handling NM integration with standard Red Hat ifcfg files.
</tp:docstring>
<method name="GetIfcfgDetails">
<tp:docstring>
Given an ifcfg file, return various internal information about it.
</tp:docstring>
<annotation name="org.freedesktop.DBus.GLib.CSymbol" value="impl_ifcfgrh_get_ifcfg_details"/>
<arg name="ifcfg" type="s" direction="in">
<tp:docstring>
The full path to an ifcfg file.
</tp:docstring>
</arg>
<arg name="uuid" type="s" direction="out">
<tp:docstring>
The UUID of the NM connection backed by this ifcfg file. If the ifcfg file does not contain a UUID tag, this UUID is generated by NM, otherwise the UUID from the ifcfg file is used.
</tp:docstring>
</arg>
<arg name="path" type="o" direction="out">
<tp:docstring>
The object path of the NM connected backed by this ifcfg file.
</tp:docstring>
</arg>
</method>
</interface>
</node>