Re: [naviserver-devel] ns_info / ns_server

2013-01-08 Thread Gustaf Neumann
Am 03.01.13 18:48, schrieb Jeff Rogers: > > Does it make sense to have 2 different information-gathering commands, > tho? Why not consolidate all these functions into "ns_info", giving > appropriate subcommands -server and/or -pool flags as necessary? well, we have as well ns_conn and ns_thread

Re: [naviserver-devel] ns_info / ns_server

2013-01-03 Thread Jeff Rogers
Gustaf Neumann wrote: > In naviserver, we have essentially the two commands "ns_info" and > "ns_server" to obtain information about the "nds" process, about a > single (virtual) server and about (connection) pools. > I would propose to make the following changes to address these problems: The ch

[naviserver-devel] ns_info / ns_server

2013-01-01 Thread Gustaf Neumann
Dear naviserver community, First, all the best in the new year! A few days ago, i have merged the naviserver-connthreadqueue fork back into the naviserver trunk, since the server is running since a few weeks flawless in our production environment. While doing some code cleanup and documentatio