On Jun 15, 2005, at 7:50 AM, Dossy Shiobara wrote:
Any ns_param in the "ns/servers" section defines a new virtual server. In this case, you defined a virtual server whose name is "dbname(test)" and its description is "test".
Whoa..... that's slightly unexpected. :) I haven't used virtual servers in eons, so had no idea how they are even set up anymore.
Of course, I don't know why you only saw a change in startup behavior moving from 4.0.8 to 4.0.10 ... but perhaps there was a "bug" that was "fixed" somewhere between the two versions.
Must have been, because this sure isn't new. In fact, many of my config files have two ns_params at the start of ns/servers, like this: ns_param staging-foo "staging-site" ns_param live-foo "live site" And then everything else in that section has a someparam(staging-foo) version and a someparam(live-foo) version. The server value would be set on the nsd command line with -s and would choose which of these sets of values was actually used. It was just a shortcut way of having only one config file per client. That stopped working a long time ago; there was a patch for it in the 3.x days, but when we moved to 4.x we had to split the config files into two. A lot of them still have the extra stuff in them for the other server, though, which up to now was just ignored by nsd (as far as we could tell, anyway). I was planning on doing some config file cleanup anyway... looks like I had better move that closer to the top of the todo list! janine -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
