Derrick
On May 16, 2009, at 12:39 PM, David Boyes <dbo...@sinenomine.net> wrote:
On 5/16/09 12:33 AM, "Jeffrey Altman" <jalt...@secure-endpoints.com>
wrote:
OpenAFS does not have a configuration file for use by
administrators to
configure the various services. As a result, each time a new
configuration option is created it has been implemented either as a
compile time option or a run time option controlled by a command-line
switch. The gatekeepers are opposed to the addition of new compile
time
options because it puts packagers in the position of determining what
features administrators and end users are able to deploy without
building from source. However, additional command-line parameters
have
their own complexity issues. For example, the current fileserver
command line has approximate forty options; many of which are no
longer
optional for reasonable deployment configurations.
Rather than scattering configuration around in files, I'd like to
see a
configuration daemon that maintained the configurations for the
various
pieces. A single command line argument identifying a set of
addresses to
contact a config daemon would make this very simple to implement,
and the
config daemon could be a simple "connect, id yourself, receive your
config,
disconnect" operation. Would make configuration management a lot
simpler.
spoofable, or do you think we *never* need to configure encryption?
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
