Skip to main content.
home | support | download

Back to List Archive

IncludeConfigFile relative path

From: Jonas Wolf <JOWOLF(at)not-real.uk.ibm.com>
Date: Wed Aug 18 2004 - 14:36:51 GMT
Given the following directory structure and files:

/one/two/index.cfg:
IncludeConfigFile ../index.cfg

/one/index.cfg:
IncludeConfigFile ../index.cfg

/index.cfg:
IndexDir stdin

I want to call swish-e -c index.cfg while in directory /one/two.
I would expect this to read /one/two/index.cfg, then include 
/one/index.cfg, and thus include /index.cfg and wait for input.

However, 

[/one/two] %swish-e -c index.cfg -v 3
Parsing config file 'index.cfg'
Parsing config file '../index.cfg'
Parsing config file '../index.cfg'
Parsing config file '../index.cfg'
Parsing config file '../index.cfg'
..

because of the relative path used in /one/index/cfg, which at runtime is 
taken relative to the execution directory /one/two and not the 
configuration file directory /one. Is there a particular reason for having 
it like this?

Jonas
Received on Wed Aug 18 07:37:17 2004