On 10/21/22 09:05, Jan Engelhardt wrote:
On Friday 2022-10-21 16:26, Lee Duncan wrote:
In the past these files went in /etc/iscsi. I have moved them to /var/lib/iscsi in Factory/openSUSE, but I have left them in /etc/iscsi for SUSE.
Something is going to expect /etc/iscsi (like a config file?), so under that consideration, you cannot move it.
(I was thinking of /etc/my.cnf for example. There is a line "datadir=/var/lib/mysql" in that file, which means you could not move /var/lib/mysql to anywhere else without breaking the setup.)
Hi Jan: Thank you for your reply! Actually, there are two types of files (in SLE) in /etc/iscsi: * Database files, and * Configuration files I do not plan to (ever?) move the configuration files. These are initiatorname.iscsi and iscsid.conf. But the database files really don't belong in /etc, and have already been moved in other distros, e.g. RedHat. These are: /etc/iscsi/ ifaces/ interface DB ifaces.example nodes/ discovered Node DB send_targets/ discovery records DB lock a lock file (I would also like to move the lock file, but I see no problem doing that) So "ifaces", "nodes", and "send_targets" contain history that should not be lost. Generally, humans don't edit these files, though they can edit them. (There are commands to do it, but some just use an editor.) I understand config files shouldn't move -- that's why we *still* have a symlink:
/etc/iscsid.conf --> /etc/iscsi/iscsid.conf
because we moved this file years ago. NOTE: I'm mostly interested in this for SLE-15-SP5. It seems like having the DB files move when upgrading to a new service pack seems reasonable, if and only if I can somehow copy the old DB files to the new location when installing my package. Is that possible? NOTE2: these DB files are already moved in Tumbleweed, and not a single user filed a bug. Perhaps that just means the package isn't used much in Tumbleweed? -- Lee Duncan