[OpenAFS-devel] parsing program options from config file(s)

[Russ Allbery]

chas williams - CONTRACTOR <chas@cmf.nrl.navy.mil> writes:
> Derrick Brashear <shadow@gmail.com> wrote:

>> Gerrit 7903 adds 2 krb5 profile-style config files,
>> openafs-client.conf (in client's etc dir e.g. /usr/vice/etc) and
>> openafs-server.conf (in server's etc dir e.g. /usr/afs/etc)

> i might ask why put them in /usr/.../etc?  i understand that
> traditionally, that is where they should go but the world is
> apparently moving to a /usr is read-only model.  configuration
> files should go in /etc along with all the other configuration files. at
> a minimum i would say search /etc first and then fall back to the old
> transarc paths.

When Derrick says "in client's etc dir" and "in server's etc dir,"
presumably that means that it follows the normal configure process for
chosing those directories, which means it will end up in
/usr/local/etc/openafs and /usr/local/etc/openafs/server by default if you
don't build with Transarc paths.

With builds like the Debian packaging, /etc/openafs and
/etc/openafs/server will be used because sysconfdir is set during
configure.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>