Bug 622797

Description of problem:
The files condor retrieves configuration from is changing for 1.3.  Previously, the global configuration file (/etc/condor/condor_config) defined LOCAL_CONFIG_FILE pointed to $(LOCAL_DIR)/condir_config.local (where LOCAL_DIR = /var/lib/condor).  We originally extended this to define LOCAL_CONFIG_DIR in LOCAL_CONFIG_FILE for use with the condor-wallaby-client package.  We tell the user to edit condor_config.local in many places in the docs for various configuration settings.

In 1.3, this is all changing.  LOCAL_CONFIG_FILE will no longer be defined by default, and instead LOCAL_CONFIG_DIR (pointing to /etc/condor/config.d) will be the sole location for configuration extension.  Files need to be placed into LOCAL_CONFIG_DIR with the parameters for the desired changes, and files should be preceded with a 2 digit number (for order).  By default, the condor package will create a 00personal_condor with configuration required for a single node pool.

So, in all places where we tell the user to edit condor_config.local in /var/lib/condor we need to tell them to edit another file instead.  As the root user, they should create a file in /etc/condor/config.d starting with the number 10 followed by the name of the feature they're enabling. So for example, if they're enabling low-latency they should create a 10low_latency file, or if they're enabling Dynamic Slots they could create a 10dynamic_slots file.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: