Whatever format is chosen, *COMMON* arguments should be able to be specified in a *COMMON* section, then overridden on a per daemon basis.
I was going nuts with the dots in principals thing, had to grep all the binaries to figure out which ones needed it turned off in, had to find the config file and add the args... And it doesn't help any when the man pages don't have the correct spellings for available options either. :-P FYI, not everyone who uses AFS is knowledgable of the KRB config file format. Some people use W2K3/W2K8 for our KRB servers. And speaking of feature requests... is there a way to add "hooks" into the pts security database lookups? Derrick Brashear wrote: > On Sat, May 16, 2009 at 9:07 AM, <[email protected]> wrote: > >> Hello Derrick, >> >> On Sat, May 16, 2009 at 08:43:40AM -0400, Derrick Brashear wrote: >> >>>> In an extreme case, if you would not be able to express some configuration >>>> choice without an elaborated syntax, then you may define an appropriate >>>> syntax and still place this data into a command line argument. >>>> >>> In some way which is arcane and not legible to the user? Why?? >>> >> I did never suggest using an arcane and unintelligible way. >> > > I had already composed a reply earlier, and junked it because I > thought Simon made the point better, but... > > Consider the case which pushed us here. You have an array of numbers. > It's a set of timeout values, which apply when you have between a > certain number of callers. > > You can, of course, just pass an argument which is a comma separated > list of timeouts. What do they mean? Well, you don't need to pass > those numbers, so, well, just make sure you order things right. > > But wait. What happens if you want to also make the ranges the > timeouts apply in tunable? Do you now pass 2 lists, one for the bucket > ranges and one for the timeouts, or a set of pairs? How do you > delineate the pairs? > > The work to allow passing arguments on the command line rapidly > devolves the syntax of those arguments to absurd. > _______________________________________________ > OpenAFS-info mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-info > -- LyX: http://www.lyx.org/ OpenOffice: http://www.openoffice.org/ Inkscape: http://www.inkscape.org/ Scribus: http://www.scribus.net/ GIMP: http://www.gimp.org/ PDF: http://www.pdfforge.org/
signature.asc
Description: OpenPGP digital signature
