Description of problem:
The source release of corosync 1.4.3 contains the following in conf/corosync.conf.example:

amf {
        mode: disabled
}

At the same time the corosync.conf(5) man page states the following about available top level options / sections in the corosync.conf configuration file:

*** BEGIN QUOTE ***
The configuration file consists of bracketed top level directives. The possible directive choices are:

       totem { }
              This top level directive contains configuration options for the totem protocol.

       logging { }
              This top level directive contains configuration options for logging.

       event { }
              This top level directive contains configuration options for the event service.

       It is also possible to specify the top level parameter compatibility. 

*** END QUOTE ***

So there appears to be an inconsistency: either the amf { } section is allowed but not documented (and the documentation is written in a way which suggests that it cannot exist), or it is not allowed / not interpreted and should thus not be found in an example configuration file.

The Corosync website at http://corosync.org/doku.php?id=support suggests that bugs against the source / upstream release should be filed here against Fedora, so I'm doing this (without having verified whether this issue actually affects Fedora, too). The example configuration file is contained unmodified in ELRepo.

Version-Release number of selected component (if applicable):
1.4.3

This issue does not affect corosync 2.0.1.