Vyatta configuration system (mirror of https://github.com/vyos/vyatta-cfg.git) https://git.amelek.net/vyos/vyatta-cfg.git/atom?h=circinus 2024-07-03T17:10:05+00:00 2024-07-03T17:10:05+00:00 John Estabrook jestabro@vyos.io 2024-07-03T15:33:52+00:00 urn:sha1:67e53cb940924693c9a80ff86c968e6fdca441d2 (cherry picked from commit d509db1020f1f18023871f4ff6149352cd69c800) 2023-05-29T08:07:39+00:00 Christian Breunig christian@breunig.cc 2023-05-29T08:07:39+00:00 urn:sha1:2a1b4b50b4c948e3234b9e985abc43f68fb6ddbf 2023-05-21T21:09:25+00:00 Christian Breunig christian@breunig.cc 2023-05-21T21:09:25+00:00 urn:sha1:bc9434237bc38a966f4b67ad2d9cf629886bc074 2023-02-13T10:25:27+00:00 sarthurdev 965089+sarthurdev@users.noreply.github.com 2023-02-12T23:19:19+00:00 urn:sha1:74e57cf02883a9e1c34df3fd17d3293e98c1fae9 Fixes compile error: void operator delete(void*, std::size_t)' called on pointer returned from a mismatched allocation function 2022-09-05T11:17:48+00:00 John Estabrook jestabro@vyos.io 2022-09-05T11:17:48+00:00 urn:sha1:3f407aa8d66dacbbf92e22673d8871e429079ce0 2022-08-13T23:35:09+00:00 RageLtMan rageltman [at] sempervictus 2022-08-13T15:34:08+00:00 urn:sha1:28cf6fee14d3bc5f6eda2099c7eb36e43297a8a8 Kernel 5.15, and probably newer, present an EXEDEV error when the vyatta-cfg code tries to boost::filesystem::copy_file on UnionFS FUSE mounts. This completely breaks operation on newer kernels, and is therefore a blocker to the rest of the project moving on to new Linux LTS versions. Boost is complex and fraught, this code behaves inconsistently in verious operating environments, and can be a nightmare to debug. Handle the concerns above using binary streaming in C++ to copy the source to the destination if an exception occurs during the existing Boost copy_file operation. Testing: Built ISO (cloud target), packer install, booted in OpenStack on KVM, booted in AWS on Xen, verified configurations are committed in both cases and that error logs are being generated to inform users about the fall-through being utilized to write-out configurations. Notes: Logging may be dropped to avoid flooding storage on often-updated systems. It is left in-place to aid developers in debugging the root concern underpinning Boot breakage (which may impact other areas of the code). 2022-05-16T12:34:05+00:00 Volodymyr Huti volodymyr.huti@gmail.com 2022-03-29T00:43:47+00:00 urn:sha1:eb304063e05967f7024fb3b2b6f0d38a7df520af 1. Use chrono library instead of basic C library to improve accuracy 2. Introduce the tracing helpers 3. Add tracing calls to the main processing points NOTE: loger is writing to the stdout, and for bootloader it is redirected to - /var/log/vyatta/vyos-boot-config-loader.log 2020-05-05T02:46:34+00:00 John Estabrook jestabro@vyos.io 2020-05-05T01:46:26+00:00 urn:sha1:dadf6384029fd6748a21832e4968261d1f7c60fd In release v1.0 of unionfs-fuse, the meta directory was renamed from .unionfs to .unionfs-fuse. Consequently, the clean up of the directory following a commit vacuously succeeds, and the meta data remains. On a subsequent commit, this hidden directory will be copied into the tmp directory structure. As permissions on the whiteout files belong solely to the user, commit actions in a multiuser environment may encounter permission errors, leading to a failure in commit. Change the meta directory name here to accord with the change in unionfs-fuse, but beware that the change is reverted in release v2.0 of unionfs-fuse. 2019-03-21T17:15:50+00:00 Christian Poessinger christian@poessinger.com 2019-03-21T17:15:50+00:00 urn:sha1:2b2010c42b827e7d119d962c7f4a1bc00900800a 2019-02-28T11:27:28+00:00 Daniil Baturin daniil@baturin.org 2019-02-28T11:27:28+00:00 urn:sha1:53659fb9e337cd1db05ff2993f7f2dcba6cb0de0