On Oct 13, 2010, at 6:36 PM, Jeffrey Hutzelman wrote: > --On Wednesday, October 13, 2010 05:32:30 PM -0400 Steve Simmons > <[email protected]> wrote: > >> IMHO the basic parameter for this belongs in BosConfig . . . > > The bosserver re_writes_ the BosConfig file on the fly. The intent is that > all changes are made by making RPC's to the bosserver.
And that rewrite is a problem for us. When the bosserver does it, our systems stop passing tripwire. We consider that failure to pass a good thing, because when our configuration changes, we kind of want to know that and capture it appropriately. Other folks' milage may vary. >> ... suggestion elided ... > > Ugh. No, we don't need a "bos put this text in the BosConfig file" command. > The BosConfig file is not intended to be edited by hand, and its format is an > implementation detail. That ugliness really doesn't need to be exposed to > the user any more than it already is. That may have been the original intent, just as original intent was that folks modify the rc scripts to change the startup parameters. Neither assumption reflects 2010. We need config files, things need to read them, tools need to re-read them, nobody but the sysadmin should be rewriting them. If it's not to be BosConfig, that's fine by me. But until somebody commits developing those more general config file, BosConfig is the obvious place._______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
