Custom Query (894 matches)

The example repo claims that the SymLink? element can be used inside a Bundle, but it can't:

/var/lib/bcfg2/Bundler/exim4.xml ***FAILS*** to verify          <----
<?xml version="1.0"?>
<Bundle name="exim4" version="2.0">
  <Group name="relay-mailserver">
    <Package name="exim4"/>
    <Package name="exim4-base"/>
    <Package name="exim4-config"/>
    <Package name="exim4-daemon-light"/>
    <Service name="exim4"/>

    <SymLink name="/etc/foo" to="/etc/bar"/>

  </Group>
</Bundle>
/var/lib/bcfg2/Bundler/exim4.xml:9: element SymLink: Schemas validity error : Element 'SymLink', attribute 'to': The attribute 'to' is not allowed.
/var/lib/bcfg2/Bundler/exim4.xml fails to validate

However, SymLink? entries can be written to Rules/*.xml:

<Rules priority='0'>
  <Group name='relay-mailserver'>
    <SymLink name="/etc/foo" to="/etc/bar"/>
  </Group>
</Rules>

... But these rules don't seem to be applied at all.

I'm updating documentation on the wiki, and I have come to the conclusion that the bcfg configuration system (for itself, not everbody else) needs work. The /etc/bcfg2.conf file seems like it should either be used a lot more or a lot less: it has a bare minimum of entries, some of which seem like they might be more appropriate in the repository's etc/ directory. The statistics section especially stands out as a weird one. The disconnect between the repository's etc/ directory and the /etc/bcfg2.conf file is alsy weird.

I'm not sure what should live where, so I have no suggestions right this moment, but I think a general cleanup of bcfg's client and server configuration would make understanding a new install that much easier.

A default bcfg2.conf file is missing from the rpm packages. We should add that (marked as a config file, of course) to help out the new users.