commit 67e4186a296775d592884584863050323e118a9b
author Andrew Geissler <geissonator@yahoo.com> Tue Apr 22 09:50:30 2025 -0500
committer Andrew Geissler <geissonator@yahoo.com> Tue Jul 29 14:22:07 2025 -0500
tree 6ddd4d4c13d935fe203551c0f06e376d0eae0d29
parent 0a95d918780602d6a88aaa9a1435c9c333f76d4a

move srvcfg-mgr.json file to /var

The srvcfg-mgr.json file is a file that tracks systemd services that the
srvcfg-mgr application monitors and controls. The file is created by the
srvcfg-mgr application on startup. The file is not meant to be modified
by users. Given that this file is not a config file modifiable by users,
move it out of /etc and into /var to better follow other OpenBMC
applications usage of the filesystem. In general, application data goes
under /var, config files which are editable by users/scripts go in /etc.

Future commits in this series will add additional configuration data
files so the goal with this commit is to first get the existing file in
the correct directory so that new files can go there as well.

Note that this is forward compatible in that when you update to code
with this commit in it, your file in /etc will be moved to /var. But if
you were to move backwards after that then the file in /var would not
be moved (the old firmware has no knowledge of it). In this case a new
file would be generated in /etc.

Tested:
- Started up fresh QEMU session, verified file was created in
  /var/lib/service-config-manager/srvcfg-mgr.json and it looked correct
- After above test, stopped srvcfg-mgr.service, moved the file from /var
  to /etc, removed the /var/lib/service-config-manager dir and then
  started up srvcfg-mgr.service. Confirmed file was moved to correct
  location under /var

Change-Id: Ida01ae960f0553bf0f4cf07fe8c3555a4a527e90
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>