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.98 2009-06-29T17:05:13+00:00 2009-06-29T17:05:13+00:00 Mohit Mehta mohit.mehta@vyatta.com 2009-06-29T17:05:13+00:00 urn:sha1:cab2d7d0a9148af414c180c4728b41e89510420f 2009-06-27T01:53:06+00:00 Mohit Mehta mohit.mehta@vyatta.com 2009-06-27T01:30:10+00:00 urn:sha1:da5e2ca70184d0254ba5cd44818c6213cbcfac9a 2009-06-26T22:08:02+00:00 slioch slioch@eng-140.vyatta.com 2009-06-26T22:05:48+00:00 urn:sha1:aa697721489c867de9b39121836c05a5bc3239b6 CREATE, DELETE, END, BEGIN) within a priority tree. That means that all work (include the commit-check pass) will be performed on a priority tree before proceeding to the next priority tree. If a priority tree generates a failure in the commit-check pass processing will halt on the priority tree and no further processing will be performed on the priority tree. The failed priority tree will NOT be copied to the active working directory. All nodes in the priority tree will execute SYNTAX and COMMIT actions except for nodes that have been deleted. Note this iteration is performed on the working tree, so all commit-check nodes will either be directly modified or have a node down the hierarchy that had been modified. The working directory and active directory will not be modified until after all priority trees have been processed. 2009-06-24T18:51:45+00:00 slioch slioch@eng-140.vyatta.com 2009-06-24T18:43:11+00:00 urn:sha1:bbf867acfcaa999dec75b3a76ca6d286db4b57f8 Note that commit check only applies in the following cases: 1) On nodes or ancestors of nodes that have been set or modified 2) Does not applied to deleted nodes Feature developers should: 1) locate commit checks at a common ancestor if checking across a hierarchy 2) expect that the commit check only enforces created behavior (therefore behaves more like a create check). An additional flag is provided "-f" to allow for full syntax and commit checks. This allows a complete single pass on all syntax and commit errors. The default behavior is to stop processing on the first error. 2009-06-19T21:10:47+00:00 slioch slioch@eng-140.vyatta.com 2009-06-19T21:10:47+00:00 urn:sha1:f625070dec4cb848d2348aeaa66c03713a4a89ee 2009-06-13T02:01:29+00:00 An-Cheng Huang ancheng@vyatta.com 2009-06-13T02:01:29+00:00 urn:sha1:f36b172142f6a52d6898ad4b32e58c4f5bb183da 2009-06-13T01:56:15+00:00 An-Cheng Huang ancheng@vyatta.com 2009-06-13T01:56:15+00:00 urn:sha1:ebad1141e86925320db2370ee49ce316c73226f5 2009-06-13T00:09:26+00:00 An-Cheng Huang ancheng@vyatta.com 2009-06-13T00:09:26+00:00 urn:sha1:b11c6a14c52e9c88b47b8160f1827f40d1f5cc17 2009-06-12T22:19:01+00:00 Stephen Hemminger stephen.hemminger@vyatta.com 2009-06-04T21:49:08+00:00 urn:sha1:6bd650f8ebcf63008a5a8dbbff19f56224857310 Bug 4501 This solves the problem that 'show interfaces ethernet' also shows pseudo ethernet (peth0) device. The problem was that peth0 matched the regex since it was missing start/end. (cherry picked from commit 71fb6be3ac3d7ce3c7f08b1408c8c9a6b9fc0422) 2009-06-12T22:19:01+00:00 Stephen Hemminger stephen.hemminger@vyatta.com 2009-06-04T22:49:36+00:00 urn:sha1:6f008c2a35b5ab2e7e85d8bd0771e5c4badab955 Move the speed/duplex setting into script where we can handle errors better, and avoid setting speed/duplex twice. (cherry picked from commit 330470f1f060f579434eb89469f4ed021c95449d)