[OpenAFS] Enabling --enable-bos-new-config unconditionally in 1.6

Russ Allbery rra@stanford.edu
Tue, 18 Aug 2009 22:37:28 -0700

I would like to cut down on the number of configure options that OpenAFS
is carrying around.  One of the pieces of low-hanging fruit is this
option, which enables a new and fairly harmless feature.

If this option is given (currently not the default), when bosserver
starts, it will look for a file named BosConfig.new in its configuration
directory.  If found, it will move it to BosConfig before reading the
configuration file.  This provides a way to stage changes to BosConfig
without running into problems caused by bosserver rewriting the existing

I'd like to enable this unconditionally in 1.6.  The only drawback that
we've been able to think of is that it will cause surprising behavior for
anyone who has a BosConfig.new file sitting around in that directory.

Does anyone have that situation right now?  Does anyone have any
objections to enabling this if that issue is mentioned in the release

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