~ubuntu-branches/debian/sid/network-manager/sid

« back to all changes in this revision

Viewing changes to system-settings/plugins/ifcfg-rh/nm-ifcfg-rh.xml

  • Committer: Bazaar Package Importer
  • Author(s): Michael Biebl
  • Date: 2010-02-22 00:31:22 UTC
  • mfrom: (1.3.4 upstream)
  • Revision ID: james.westby@ubuntu.com-20100222003122-61x6conwdfahw6ab
Tags: 0.8-1
* New upstream release.
  - ifupdown: don't export connections until "managed" state is checked.
    (Closes: #568287)
* Remove patches, all merged upstream
  - debian/patches/03-hostname-fallback.patch
  - debian/patches/04-etc-hosts-rewrite.patch
  - debian/patches/05-ifupdown-allow-hotplug-autoconnect.patch
* debian/network-manager-dispatcher.script
  - Map NetworkManager down event to ifupdown post-down phase.
    (Closes: #562811)
  - Map vpn-up/vpn-down event to ifupdown post-up/post-down phase.
    (Closes: #518530)
  - Comment out pre-up/pre-down events as they are not supported upstream.
  - Add hostname event but don't hook it up with a particular action.

Show diffs side-by-side

added added

removed removed

Lines of Context:
 
1
<?xml version="1.0" encoding="UTF-8" ?>
 
2
 
 
3
<node name="/" xmlns:tp="http://telepathy.freedesktop.org/wiki/DbusSpec#extensions-v0">
 
4
    <interface name="com.redhat.ifcfgrh1">
 
5
      <tp:docstring>
 
6
          Utility methods for handling NM integration with standard Red Hat ifcfg files.
 
7
      </tp:docstring>
 
8
 
 
9
      <method name="GetIfcfgDetails">
 
10
        <tp:docstring>
 
11
          Given an ifcfg file, return various internal information about it.
 
12
        </tp:docstring>
 
13
        <annotation name="org.freedesktop.DBus.GLib.CSymbol" value="impl_ifcfgrh_get_ifcfg_details"/>
 
14
        <arg name="ifcfg" type="s" direction="in">
 
15
          <tp:docstring>
 
16
            The full path to an ifcfg file.
 
17
          </tp:docstring>
 
18
        </arg>
 
19
        <arg name="uuid" type="s" direction="out">
 
20
          <tp:docstring>
 
21
            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.
 
22
          </tp:docstring>
 
23
        </arg>
 
24
        <arg name="path" type="o" direction="out">
 
25
          <tp:docstring>
 
26
            The object path of the NM connected backed by this ifcfg file.
 
27
          </tp:docstring>
 
28
        </arg>
 
29
      </method>
 
30
    </interface>
 
31
</node>