Re: [Condor-users] What happens if a file on the LOCAL_CONFIG_FILE list cannot be parsed?

["Ian Chesal" <ICHESAL@xxxxxxxxxx>]

> The manual section that talks about LOCAL_CONFIG_FILE
>
(http://www.cs.wisc.edu/condor/manual/v6.8/3_3Configuration.html#11793)
> doesn't mention what happens if one of the files in the list does not
> exist. For example, if I have:
> 
> LOCAL_CONFIG_FILE = $(LOCAL_DIR)/filethatexists.1,
> $(LOCAL_DIR)/filethatdoesnotexist.1, $(LOCAL_DIR)/filethatexists.2
> 
> Do filethatexists.1 and filethatexists.2 get parsed or does Condor
stop
> parsing files on the list when filethatdoesnotexist.1 cannot be found?

To answer my own question: my tests indicate that 6.8.x Condor doesn't
stop parsing the list of files when it encounters a config file that
doesn't exist. It keeps parsing the rest of the files in the list. So
filethatexists.1 and filethatexists.2 both get parsed for configuration
information.

- Ian


Confidentiality Notice.  This message may contain information that is confidential or otherwise protected from disclosure.
If you are not the intended recipient, you are hereby notified that any use, disclosure, dissemination, distribution, 
or copying of this message, or any attachments, is strictly prohibited.  If you have received this message in error, 
please advise the sender by reply e-mail, and delete the message and any attachments.  Thank you.