On Wednesday 05 February 2003 03:36 pm, Charles Steinkuehler wrote: > This works fine for things like ifconfig/route, and even > iptables/ipchains, where the built configuration resides in memory, but > it begins to fail when configuration is via a file on the "disk". Using > dhcpd as an example, not only does the configuration file have to be > intelligently updated if a variable it depends on changes, something has > to restart (or HUP or whatever) the daemon to get it to recognize it's > config has been updated.
Duly noted. Where does the responsibility of the 'check' and 'restart' lie? This would seem to be the respnsibility of the back-end (save-script), on first glance. Would a "trigger" be a good method? Would a seperate db need to be made to keep track of "triggers" and the needed information? I'm assuming a dynamic db based on a list of used variables contained in the package itself. Thoughts? > I think the best general solution so far has been presented by Chad > Carr. A templating system, combined with a configuration database or > tree, allows boot-time creation of customized configuration files from > standard (unmodified from distribution form) pacakges and localized > configuration information. With a standard package <> congifutation > API, the configuration system can support "callbacks" or similar, > letting a package know when values it depends on have been modified, > triggering a rewrite of the configuration file, the restarting of a > daemon, or whatever else might be necessary. With some playing, I'm starting to agree with this to a point. A tree that contained '/path/variable/value' would be simple to set and change. However pairing the variable/value might not be too fun to use in the files that use this infomation. Considering this, if there was an added single db file that would concentrate the tree db information, there would be an option to easily find 'where' to change a value (by hand) and location to source for the run-time packages themselves. Let's say something like this: /db-tree/interfaces/eth1/ip_address (contains 192.168.1.254) /etc/db.cfg contains: PREFIX=/db-tree LAN_IP='cat /$PREFIX/interfaces/eth1/ip_address' Then the application uses: source /etc/db.cfg #Internal interface ip address to use $LAN_IP Thoughts??? -- ~Lynn Avants Linux Embedded Firewall Project developer http://leaf.sourceforge.net ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
