Custom Query (894 matches)

The bcfg client (or maybe server?) should give a warning if there are duplicate entries. From my experience, this happens if one creates a Bundle and then forgets to remove a ConfigFile? or Package from outside the bundle. Without a warning like this, it might be hard for the user to find the error. (The actual error seen by the user might be eg. that debsums still says "Package foo failed validation. Bad files are: ...".)

Some duplicates might be hard or even logically impossible to find due to inheritance/priorities, but any progress on this subject would be good. There are trivial cases where the bcfg2 client actually prints the entries multiple times:

In dryrun mode: suppressing entry installation for:
 ConfigFile:/etc/mysql/my.cnf           ConfigFile:/etc/mysql/my.cnf

At least these should be easy to catch.

Should some of the bcfg2-server plugins only look for *.xml files in configuration dirs? They already omit *~ but not eg. #foo.xml# which is an auto-save filename format for the jed editor.

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.