From: Daniel P. <da...@ri...> - 2004-08-05 07:30:03
|
On 5 Aug 2004, Craig Barratt wrote: > Daniel Pittman writes: >> On 5 Aug 2004, Michael Pellegrino wrote: >>>> On 5 Aug 2004, st...@36... wrote: >>>>> Quoting Daniel Pittman >>>>>> On 4 Aug 2004, Steve wrote: [...] >>>> Also, it is worth noting that files named >>>> '/etc/backuppc/<host>.pl' work >>>> for this, and they are what I prefer to use. :) [...] > It's an undocumented feature. BackupPC merges the following three > config files in order: > > __TOPDIR__/conf/config.pl > __TOPDIR__/conf/HOST.pl > __TOPDIR__/pc/HOST/config.pl > > Settings in later files override the earlier files. So the per-PC > host file can go either in __TOPDIR__/conf/HOST.pl (undocumented) > or __TOPDIR__/pc/HOST/config.pl (offical documented location). > > Daniel, I assume you have a symlink from __TOPDIR__/conf to > /etc/backuppc. Checking says no, I don't. Presumable the Debian packager either configures or patches BackupPC to conform to Debian policy about configuration files... > That said, now that I am implementing a CGI config editor, it is > difficult to have the per-PC config file in two places. Where do > you write the config file? So the config editor might not support > the undocumented __TOPDIR__/conf/HOST.pl location. ...which is that all configuration must live under /etc somewhere. I suspect I found the undocumented feature, initially, by just putting the config file there and having it work. :) Personally, I agree with the Debian decision to house all configuration under /etc, and would encourage you to use that as the default location for all configuration -- including the config.pl file -- by default. Regards, Daniel -- What is art but a way of seeing? -- Thomas Berger |