The real question is not why it is the way it is (unless there's one that prevents it from being changed), but what would it take to change it to read a config file at runtime instead of it all being compiled in? Editing a config file to change a path, device, or hostname would be much easier than a recompile. Especially when you find that the compile options you set don't work (portranges come to mind, amanda won't run if the tcp and udp ports are not lower or higher than some unknown value). You can aleady make quite a few changes with command-line options, so parsing a config file shouldn't be any harder than parsing the command line.
Frank --On Friday, December 07, 2001 09:37:20 -0500 Joshua Baker-LePain <[EMAIL PROTECTED]> wrote: > On Fri, 7 Dec 2001 at 9:06am, Eric Veldhuyzen wrote > >> So please explain to me, what is so great about setting this all at >> compile time instead of in a configuration file so that it can be >> determined at runtime? > > I certainly can't give a definitive answer to this. I *can* tell you that > this question pops up every now and then, so you can search through the > archives for previous discussions it. I was going to offer some guesses > here, but it really wouldn't help. > > -- > Joshua Baker-LePain > Department of Biomedical Engineering > Duke University -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
