Synopsis: When run with -f <conf> flag, runs MUCH quicker than with compiled in conf location
State-Changed-From-To: open-feedback State-Changed-By: [EMAIL PROTECTED] State-Changed-When: Sun Mar 30 07:12:26 PST 1997 State-Changed-Why: The configuration files are read in once during startup, and then not referenced again until a reload is requested. How they are located should have no impact on server performance once they have been loaded. Can you confirm that you are still seeing this problem, it is reproducible, and that it isn't a process priority issue?
