Mailinglist Archive: opensuse-bugs (5243 mails)

< Previous Next >
[Bug 800956] Iscsi Target configuration with YAST fails due wrong filedirectory

https://bugzilla.novell.com/show_bug.cgi?id=800956

https://bugzilla.novell.com/show_bug.cgi?id=800956#c5


--- Comment #5 from Thomas Fehr <fehr@xxxxxxxx> 2013-03-25 20:58:18 UTC ---
(In reply to comment #4)
Thomas: yes, the directory moved to /etc/iet. But there was supposed to be a
symlink /etc/ietd.conf to /etc/iet/ietd.conf, and it looks like I left that
out.

Would such a symlink have averted this problem? If so, I will file a bug right
away and add that symlink.

The symlink would have helped but you cannot simply package it into
RPM. If the file /etc/ietd.conf exists it cannot be replaced by a symlink
during update (afaik RPM refuses to do that). You need to add a postinstall
script that does the following:
- if /etc/ietd.conf exists and /etc/iet/ietd.conf does not exist, move
/etc/ietd.conf to /etc/ietd
- create a symlink /etc/ietd.conf to /etc/iet/ietd.conf
- add symlink /etc/ietd.conf as %ghost to package
- if both /etc/ietd.conf and /etc/iet/ietd.conf exist I would suggest
to save /etc/ietd.conf to /etc/ietd.conf.save and also create the
symlink

The above needs to be done for 12.2 and 12.3 (btw. what about SLES?)

For post 12.3 you can simply move /etc/ietd.conf to /etc/iet/ietd.conf
in postinstall and I will change yast2-iscsi-client to use /etc/iet/ietd.conf

Sounds that reasonable?

--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >