Here's an idea: make a directory like "config" for the nsd stuff. Have a main file there, plus a bunch of module config files. All of the module config files get sourced by a loop in the main file. This would eliminate having to list the modules in the main file and also have a config section for them. To delete a module, rename the config file. To add a module, copy in the config file, or touch it to create an empty config file. It would also let developers publish config files for their modules/extensions, if required.
One specific area that is clumsy for us is IP aliases. It'd be nice to say in 1 line: ipalias xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx:8080 xxx.xxx.xxx.xxx Doing that with the nssock config directives is messy. Jim > Has anyone worked on improving the default nsd.tcl file structure? For > new users, and for users wanting to try something new, the lack of > documentation and default values for the different modules makes > experimentation difficult. > So here are some random thoughts: > Move module configuration into separate files. Handle all explaination > and variable setting at the top of these files, source the module file > iff it is actually used in the main nsd.tcl file. > > Or do the same with a single file, but enclose the module sections > inside ifs conditioned on whether the module is used. > > My overall impression is that some solution that allowed the developer > to concentrate on the top part of the file for setting well named, and > maybe commented, variables would be much easier to setup and maintain. > > --Tom Jackson >
