[bind10-dev] b10-cfgmgr --data-path behavior

Jelte Jansen jelte at isc.org
Fri Apr 13 08:19:42 UTC 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/13/2012 12:58 AM, Jeremy C. Reed wrote:
> (resending forgot subject line)
> 
> The b10-cfgmgr manual says about --data-path:
> 
> <para>The path where BIND 10 looks for files. The configuration
> file is looked for here, if it is relative. If it is absolute, the
> path is ignored.</para>
> 
> I think the behavior is: if --config-filename is also set and is an
>  absolute path to an existing file, then --data-path is ignored and
> the directory where the configuration is located is used instead.
> 
> Why this behavior? Is manpage correct?
> 

That manpage text can be interpreted as correct, but should be more
explicit ('relative' and 'absolute' there are about the other flag
- --config-file, not about --data-path).

IIRC the intent was that --data-path it allows you to only specify a
directory (and use the default file name there). I think the current
behaviour is almost fine, but we can improve it;
1. warn (or even error) if --data-path and an absolute --config-file
are given
2. allow relative paths in --config-file if --data-path is NOT given
(this does not work right now and has bitten me)
3. log the full file (once it has been, er, absolutilized) that is
used on startup (INFO? "cfgmgr starting with config from /path/to/file")

Jelte
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+H4Z4ACgkQ4nZCKsdOncWw4ACgtojFCE8arQ96LlbnXkovTV+m
4qQAoMnfvXf6qqBIhJWkYMk6vX6xuCm2
=Np5D
-----END PGP SIGNATURE-----


More information about the bind10-dev mailing list