[OpenAFS-devel] parsing program options from config file(s)
chas williams - CONTRACTOR
chas@cmf.nrl.navy.mil
Tue, 31 Jul 2012 10:31:44 -0400
On Mon, 30 Jul 2012 14:05:56 -0400
Derrick Brashear <shadow@gmail.com> wrote:
> On Mon, Jul 30, 2012 at 2:02 PM, chas williams - CONTRACTOR
> <chas@cmf.nrl.navy.mil> wrote:
> > On Mon, 30 Jul 2012 11:52:08 -0400
> > 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.
>
> if your packages already put e.g. CellServDB elsewhere, the files will
> end up in the same directory.
> it's just a dirpath-using thing. it already adapts if you're adapting
> other things. it's not hardcoded.
>
> in transarc-paths land, you get those paths. otherwise, you get something else.
> already solved problem.
i like having the afs server binaries in /usr/afs instead of in a place
a user might typically have in their search path (yes, i know -- dont
have users on your fileservers) i dont really enjoy having the config
files there. how about an option (like -C/--configpath) to tell the
servers where to look for the config files and then in the config files
i could further configuration locations of things like '/usr/afs/db'.