Description of problem:
We should store sysconfig keys in a sub directory of /var/lib/matahari just to keep the data dir somewhat clean. If the user runs a bunch of sysconfig jobs, the directory will have a bunch key file in it.
[root@localhost ~]# cd /var/lib/matahari/
[root@localhost matahari]# ls
31YU6 6T3U7 8BS00 B7OBI DK3BD IJ0UA JTGJB MG7FY P9WNU systemId TZ5IJ Y3B3D
336U9 6WQAA 8MRDK C2UVW FOL8Y IYPWH JZ4CD O7Q0B sadkjlkwjwe T50LW UJ7YT ZMQQK
60F2O 7DKQL A6KNB dave's $$$ GSOU1 JNQNI lock OVQMO SDX0T TG871 W0INM ZTAH5
Version-Release number of selected component (if applicable):
I consider this a bug.
This prevents us from being able to reliably store anything else other than keys in this directory. Otherwise, whatever else we put there will get mixed up with the key files.
I propose /var/lib/matahari/sysconfig-keys/
good 2 go...
[root@pe6950-01 matahari]# ll
-rw-r-----. 1 qpidd qpidd 0 Sep 27 10:35 lock
drwxr-xr-x. 2 root root 4096 Sep 27 18:28 sysconfig-keys
-rw-r-----. 1 qpidd qpidd 37 Sep 27 10:35 systemId
[root@pe6950-01 matahari]# cd sysconfig-keys/
[root@pe6950-01 sysconfig-keys]# ls
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
No description required.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.