Re: Include in sw.conf oddity

On Sat, Nov 13, 2004 at 08:07:22AM -0800, Drew Csillag wrote:
> I've just noticed that if you have the configuration of your logfile
> paths not in the sw.conf file but in a file included from it using
> Include(...), that it doesn't honor the value in the included file. 
> I'm still looking into it, but if anyone has any ideas, it would be
> appreciated.  For now though, I'll just follow the "Doctor, it hurts
> when I do this" remedy.

I'm sure you are seeing a problem, but it must be a bit more complex
than what you've described.

I've just done the following:

  1. Done a fresh skunkweb install.
  2. Copied the log paths into a new file, "log.conf",
     and modified them slightly (adding "1" as a suffix to each 
     filename).
  3. Include-d the complete path to log.conf.
  4. started skunk.

The log files generated have the modified path.  So when other factors
are removed, I can't reproduce your bug.  There must be something else
going on in your case.

Also, if sw.conf contains definitions of those variables *before* the
Include, the include wins.  (If they contained definitions *after* the
Include, the include would lose, though.)

If you can come up with a recipe for reproducing this bug, I'd like to
fix it!

Cheers,

j

-- 
Jacob Smullyan

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBljYuuqamFyFXXLIRAvRiAJ99AFP07NsAuYFw5+jCLGt57lWSaACffX3w
lxaBV9/34eX2W3szk5EQlc4=
=yXcS
-----END PGP SIGNATURE-----