vyatta-cfg.git/src, branch debian/0.14.34 Vyatta configuration system (mirror of https://github.com/vyos/vyatta-cfg.git) https://git.amelek.net/vyos/vyatta-cfg.git/atom?h=debian%2F0.14.34 2009-03-03T06:28:16+00:00 added fix for nested priority and deletion failure. also priorities should not reside 2009-03-03T06:28:16+00:00 slioch slioch@eng-140.vyatta.com 2009-03-03T06:28:16+00:00 urn:sha1:8a66041f90db8205db50fd83aed8001175c787ed on node.tags, but on parent (node name of multinode)--this is to prevent priorities splitting behaviors between different priorities on multinodes. fixed preservation of def file when committing configuration. default leafs 2009-03-02T17:51:39+00:00 slioch slioch@eng-140.vyatta.com 2009-03-02T17:51:39+00:00 urn:sha1:f99deef50eda86d063338c92ceed768b5578fb0b configured by system will now be suppressed via show command (same behavior as with old commit). fixed node walk for delete of nodes--error introduced when adding ordering indirection for actions in commit head. 2009-02-28T04:49:57+00:00 slioch slioch@eng-140.vyatta.com 2009-02-28T04:49:57+00:00 urn:sha1:183f624fe155f518f97efc2883fc7894979950e1 Bug found when review policy_bgp regression failure. Added environment variable that can be accessed in executing node.def script to check whether commit is in a delete or set action. The environmental variable is 2009-02-27T19:45:47+00:00 slioch slioch@eng-140.vyatta.com 2009-02-27T19:45:47+00:00 urn:sha1:f0c5876c1203da45081d588fa2daf6b034281cba "COMMIT_ACTION" the value can either be "SET" or "DELETE". The variable is set for the duration of the call being made to the action in the node.def file. This should allow some simplication of scripts (i.e. such as setting up static routes). new option added to commit to disable partial commit behavior. This allows the 2009-02-27T01:18:15+00:00 slioch slioch@eng-140.vyatta.com 2009-02-27T01:18:15+00:00 urn:sha1:c484e8f1eecc8812803612d7e21e27104f839f49 user to support the 'old' cli behavior if desired via the -o flag. handle seg violation if an empty line is found in the priority file. 2009-02-26T19:56:12+00:00 slioch slioch@eng-140.vyatta.com 2009-02-26T19:56:12+00:00 urn:sha1:34293dcc8968aed3ffc0e3cee754b2e86dd566f9 cosmetic changes, and better to not leave interfaces root node under default priority. 2009-02-25T19:08:19+00:00 slioch slioch@eng-140.vyatta.com 2009-02-25T19:08:19+00:00 urn:sha1:1eef25550d68988d5299685ff6015c07d70a7e6e harvesting dead code. 2009-02-25T18:24:44+00:00 slioch slioch@eng-140.vyatta.com 2009-02-25T18:24:44+00:00 urn:sha1:d40c4e1765835dfc6509d10b15e39dbb6c5ec9b9 nested priority case under interfaces need mkdir with -p option to set 2009-02-25T18:04:52+00:00 slioch slioch@eng-140.vyatta.com 2009-02-25T18:04:52+00:00 urn:sha1:b68727e0a5612412750fbd8b1f784c040f22239f up parent directories before parent priority is visited. replace unionfs synchronization code with piecewise copy. this should fix most of the problems related to nested priorities (but not all). also moved node profiling output from debug file 2009-02-24T21:08:52+00:00 slioch slioch@eng-140.vyatta.com 2009-02-24T21:08:52+00:00 urn:sha1:91a4c9f9093a5ef5d0baf792dd94a3f4e15d4488 to stdout (when enabled by the -c flag).