On 08/07/2014 03:19 PM, Ben Cotton wrote: [Sorry, misunderstood the PRECEDENCE thing] > True, but you should only have to do it once. Future RPM-based > installations should see that condor_config.local differes from what > was shipped in the RPM and save new entries as > condor_config.local.rpmnew. It does. Can you guarantee that no condor_config.local.rpmnew will ever have a new knob that the latest condor needs? It shouldn't -- just like the order in which these files are read shouldn't change. (And if it never changes, why ship it with the rpm in the first place.) -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
Attachment:
signature.asc
Description: OpenPGP digital signature