On 9/7/06, Vlad Seryakov <[EMAIL PROTECTED]> wrote:
- if no servers defined, it will run server "default", i.e. it silently creates server "default" in config section "ns/servers"
Er, no. No crazy magic to auto-create config behind your back. Virtual servers just aren't complicated. They're a feature, and they're embedded deeply into the core code (all the references to char *server in the C API) so it's not going any where quickly. I agree with your over all goal, which is to have a minimal config file able to boot and run a functional server, right? This is definitely a good idea. The current sample-config.tcl doesn't handle this case well, and it shouldn't -- it's supposed to be a complete reference to all config values. So, we need some other way to handle basic servers. Magic config construction just isn't the way to do it though. How about we move nsd-min.tcl you just added to contrib (dumping ground, grrr...) into the top level, and call it simple-config.tcl? We'll have two config files ship by default: sample-config.tcl -- Exhaustive list of all config variables simple-config.tcl -- Basic config needed to run a single virtual server. They will be identical in the sense that the resulting running server will have the same properties, because the sample-config.tcl will be illustrating *optional* config values, and possibly they''' all be commented out. We can rename 'server1' to 'default' if you like.
