Custom Query (894 matches)

When drivers are not specified on the command line or in bcfg2.config file the following Traceback occurs. Traceback (most recent call last):

File "/usr/sbin/bcfg2", line 235, in <module>

client.run()

File "/usr/sbin/bcfg2", line 218, in run

self.tools = Bcfg2.Client.Frame.Frame(self.config, self.setup, times)

File "/usr/lib64/python2.5/site-packages/Bcfg2/Client/Frame.py", line 49, in init

if self.setupdrivers?:

KeyError?: 'drivers'

The mtime fix in the POSIX driver is being applied unconditionally. I get the following for every Config file. There are no mtime attributes set in my info files.

Installing ConfigFile /etc/motd
ConfigFile /etc/motd mtime fix failed
Installing ConfigFile /etc/ntp.conf
ConfigFile /etc/ntp.conf mtime fix failed

It should only be done if an mtime attribute was present. Which at that point in the code looks like only if mtime != '-1'

Contents of configuration files can be controlled per group/host, but not the metadata associated with them, e.g. user/group/mode/mtime.

Different config files often have different owners (like apache vs httpd or exim vs mail), so it would be nice to allow different file metadata for different groups/hosts.