Am 2015-01-25 17:16, schrieb Michael Biebl:
Am 25.01.2015 um 15:43 schrieb Ritesh Raj Sarraf:
I've still kept the systemd folks in the loop, hopefully they may be
able to shed some light.
I'd start by looking at the fedora package and see how the package is
integrated into the systemd boot process there. I notice it ships the
following files:
/lib/systemd/system/iscsi.service
/lib/systemd/system/iscsid.service
/lib/systemd/system/iscsid.socket
/usr/lib/tmpfiles.d/iscsi.conf
Using socket activation might make it possible to avoid any service
interdependencies.
In this case, that doesn't help, since the problem is not really
whether iscsid is running, but rather when the iSCSI logins are done.
Basically, Fedora has
- iscsi.service: log in to iSCSI targets
- iscsid.service: start/stop iscsid
Debian's open-iscsi.service does both. But while making iscsid socket
activatable might be something to look at in principle, it won't solve
this problem, because it's about ordering of the log ins related to
remote-fs{,-pre}.target. Btw. just looking at iscsi.service in Fedora,
they do:
Before=remote-fs-pre.target
which is the same thing my fix does in this bug report.
(+ they also do Wants=remote-fs-pre.target, because of some private
bugs in their bugtracker, which seems to be unnecessary for Debian,
since remote-fs.target pulls in remote-fs-pre.target anyway)
But thanks for taking a look at it!
Christian
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
