Hi Guys At 10:01 06.02.2003 -0600, you wrote:
Wouldn't some kind of 'dirty' flag on a package be sufficient? Once you finish the configuration all packages with that flag could be restarted.On Wednesday 05 February 2003 03:36 pm, Charles Steinkuehler wrote: ....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?
For a single key=value file there is one already in Bering and I believe in Dachstein too, lrp.conf , why not use it? It only contains parameters we need to use anyway...... 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.
If a hierarchical setup is chosen the directory idea is simple and easy to parse, but more difficult for Joe Average to read and find things in. Just refer to the /proc directory structure.
Another thought, maybe too late, I was wondering how a package like shorewall could take its parameters from a pure key=value db. The keys would have to be very elaborate then and such a set up might be more complicated to understand than the current one. Tom probably had good reasons to split his configuration files.
Thoughts....
Erich
THINK
Püntenstrasse 39
8143 Stallikon
mailto:[EMAIL PROTECTED]
PGP Fingerprint: BC9A 25BC 3954 3BC8 C024 8D8A B7D4 FF9D 05B8 0A16
-------------------------------------------------------
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
