On 2012-06-06 17:45, Jeffrey J. Kosowsky wrote:
> I am able to achieve most of what you wish by doing most of my
> customization in the individual host-specific config files since
> variables set there override variables set in config.pl
> 
> Alternatively, one could add a line of perl code at the end of the
> master config.pl file to source a set of customizations that would
> again overwrite the defaults. Then after an upgrade, you would only
> need to add back that sourcing line

The standard behaviour is that the daemon uses a default value if no
setting is found in the config file. Config files are for configuration
(away from defaults). Unfortunately, this isn't the case here.

Regards,
Tyler

-- 
"In all life one should comfort the afflicted, but verily, also, one
should afflict the comfortable, and especially when they are comfortably,
contentedly, even happily wrong."
   -- John Kenneth Galbraith

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/