On Thu, Sep 03, 2009 at 03:00:37PM -0500, Carl Wilhelm Soderstrom wrote: > On 09/03 08:45 , Davide Brini wrote: > > I agree that it should work like that. However, if I'm not mistaken, it > > seems > > that what's written here still applies: > > > > http://osdir.com/ml/sysutils.backup.backuppc.general/2003-10/msg00010.html > > I think the current behavior is the correct behavior -- where the per-host > config file variable data completely replaces the defaults set in the > config.pl. > > The reason is that there are some settings in config.pl where is it not > sensible to add the value in config.pl to the value in the per-host file; > such as the rsync command.
> It would be bad from a discoverability standpoint to have some variables be > additive, and others ablative. They should all behave the same way; and the > only sensible way IMHO is current behavior. But maybe the global config could be made available as $GlobalConf{xyz} within the per-host config? I remember having tried the same thing - that is, I want a set of default excludes, then extend then for one host. Currently, I have to repeat the whole default config just to append one more directory to the excludes. Bye, Tino. -- "What we nourish flourishes." - "Was wir nähren erblüht." www.lichtkreis-chemnitz.de www.craniosacralzentrum.de ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/