In the version we did for AOLServer 3.4.2, which relies on our
proprietary event-notification subsystem, we:
(1) Put a place in the startup .tcl script where over-rides from a local
file would be used (using "source"). That way, the file output from live
settings could be the equivalent of:
ns_section "x"
ns_param p v
...
without changing the file we ship for customers. This made it somewhat
easier to edit with Tcl (since it only uses these two commands and is
always generated, not hand-edited).
(I say "the equivalent" above because we do some fairly strange things
to map between sections/parameters and our configuration "topicspace"
that I don't want to go into here.)
(2) Our configuration variables are marked with whether they are "no
restart" or not. The backend that implements "change this variable"
returns a flag indicating whether restart is required, and our GUI puts
an indicator up if that's happened. Actually, we also set another
global state variable to "configuration changes make restart required"
so any instance of any console can show an appropriate flag.
This mostly works OK, though we do occasionally have to train
administrators with the question "When you changed that, did the console
tell you you needed to restart? What happened when you restarted?"
As far as calculated or enabled configuration settings go, we model all
of those as "restart required" settings.
-- ReC
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Jeff Rogers
Sent: Monday, October 15, 2007 12:54 PM
To: naviserver-devel@lists.sourceforge.net
Subject: Re: [naviserver-devel] ns_config read/write
Vasiljevic Zoran wrote:
> Do you have some other idea how (if) we should build the chnageable
> config? It seems pretty silly to me that we need to restart the server
> to change some marginal parameter... In the 21. century...
However this gets resolved, I think there should also be a way to easily
write out a config file based on the current dynamic configuration, so
that if the server does get restarted the configuration can stay the
same.
-J
------------------------------------------------------------------------
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
