tree 2ee2ed437121af75525c3b93a731b99e0b1c710a
parent 14498b76ca826437828c3d75afe205068e4736a6
author Jan Kundrát <jan.kundrat@cesnet.cz> 1685996836 +0200
committer Jan Kundrát <jan.kundrat@cesnet.cz> 1687386346 +0200

be more careful when dumping sysrepo configuration

I've seen one lab device with a zero-size JSON file, which obviously
cannot be restored. That's fishy and this should not happen, so let's
try to be a bit more robust when creating that file:

- do not overwrite in place (which might hit a FS race and cause an
  empty file)
- check that sysrepocfg produced "some data" (if it crashed early
  enough, it would previously still have been an empty file due to the
  output redirection)

The actual writeout is a bit more involved than I would prefer, and
because I want locking (thanks, Tomas), I think it's easier to use two
scripts for this one.

Change-Id: I43fccd3a49cae77f88b282ccac07471453910c25