vyatta-cfg.git/src/common/defs.h, branch rollingVyatta configuration system (mirror of https://github.com/vyos/vyatta-cfg.git)
https://git.amelek.net/vyos/vyatta-cfg.git/atom?h=rolling2011-03-03T23:17:40+00:00remove deactivate-handling code from commit2011-03-03T23:17:40+00:00An-Cheng Huangancheng@vyatta.com2011-03-03T23:17:40+00:00urn:sha1:84d379b8b8d3537a82d12d7b734209bef6c4ee63
* activate/deactivate is pending redesign, so the old code no longer applies.
* conceptually activate/deactivate should be transparent to commit so removing the old code.
1) Ordered evaluation of these scripts similar to what is found in2010-11-19T01:03:06+00:00Michael Larsonmike@vyatta.com2010-11-19T01:03:06+00:00urn:sha1:6ec4dddcd88975a31358983bfcebdb2c6459563e
/etc/rc* system. An integer at the beginning of the script identifies
the order in which the script is executed (i.e. 01test is run before
55monkey).
2) There is now a pre-commit hook that can be used. These scripts are
located at: /etc/precommit and are invoked before commit has started
processing actions.
3) A success/failure environment flag set before a process has run has
been changed to a tri-state:
SUCCESS = all priority groups succeeded
FAILURE = all priority groups failed
PARTIAL = mixed success/failed
change first, last, firstlast behavior to apply environment setting on each action applied. will be used to help resolve problems identified w/ fw synchronization of rules.2010-10-29T19:00:45+00:00Michael Larsonmike@vyatta.com2010-10-29T19:00:45+00:00urn:sha1:d5abfc00dcf2e606fbac6eca78eea06ead233a12add commit hook directory.2010-06-05T16:48:06+00:00Michael Larsonslioch@slioch.vyatta.com2010-06-05T16:48:06+00:00urn:sha1:6fcaf773333e0285464e774751c95b79ec9c4ff5
The entitlement bug can be fixed https://bugzilla.vyatta.com/show_bug.cgi?id=5354 by adding a hook into this directory.
initial working version of activate and deactivate: load,save,show,commit supported.2010-05-05T00:54:56+00:00Michael Larsonslioch@slioch.vyatta.com2010-05-05T00:54:56+00:00urn:sha1:0ffdc5e6d89f9677694a8eef916b07c089264753support for PARENT reference in priority statements. Example:2010-04-22T20:34:17+00:00Michael Larsonslioch@slioch.vyatta.com2010-04-22T20:34:17+00:00urn:sha1:b72ddf64bc5d89487ffe9672f0ba89c5b90ac2e5
priority: PARENT
Means that this priority group will adopt the priority value of the parent. And the behavior on deletion of this priority root node will be deleted before the parent. On
all other operations this node will be scheduled after the parent.
This should fix problems in scheduling creation/deletion orders for priority groups so long as they are located within the same hierarchy.
priority.pl has been updated as well.
fix for bug 2176.2010-04-13T18:50:23+00:00Michael Larsonslioch@slioch.vyatta.com2010-04-13T18:50:23+00:00urn:sha1:7c03bbb617c8e8c5bc9a553f25b79d43a8e40623
Embedded leaf nodes can now be supported in the cli structure. In additional an arbritrary limit can be set on the number of multinode values allowed.
Format in the node.def is:
tag: [u32]
or
multi: [u32]
For the special case of a leaf node the value for u32 is 1. In this case the operation applied to the node is to replace the node with the set value. This generates a
delete of the old tree structure from the embedded leaf and a set of the new tree structure from the embedded leaf.
dismantle old priority file parsing and node matching code. removed2009-10-23T17:07:54+00:00sliochslioch@eng-140.vyatta.com2009-10-23T17:07:54+00:00urn:sha1:a4a15d2cb93e9fcf56f98472694e064d82c31f94
references to old values.
activate priority values from node.def. priority file is now no longer used and should be considered depricated.2009-10-22T22:36:22+00:00sliochslioch@eng-140.vyatta.com2009-10-22T22:36:22+00:00urn:sha1:ee4800de96b1fb561a1e3f612814784891b4c468pull priority from file into data structure2009-10-21T23:33:13+00:00sliochslioch@eng-140.vyatta.com2009-10-21T23:33:13+00:00urn:sha1:7c64f480f3aaa2f6d46bf3d83c62e084e9a3154e