https://bugzilla.novell.com/show_bug.cgi?id=846945 https://bugzilla.novell.com/show_bug.cgi?id=846945#c0 Summary: open-iscsi should be updated to start when needed using systemd Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: All OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: lduncan@suse.com ReportedBy: lduncan@suse.com QAContact: qa-bugs@suse.de CC: hare@suse.com, meissner@suse.com, werner@suse.com, michaelc@cs.wisc.edu, fcrozat@suse.com, fxzhang@suse.com Depends on: 821695,827654 Found By: Development Blocker: --- +++ This bug was initially created as a clone of Bug #827654 +++ +++ This bug was initially created as a clone of Bug #821695 +++ Now that open-iscsi has been integrated with systemd in openSUSE, it now has reduced functionality compared with earlier versions, a clear regression. The open-iscsi service used to be installed, when based on system V init, as enabled. As part of the integration process with systemd, open-iscsi has been modified so that it is now socket activated. This means that, in conjunction with systemd, the iscsi service need not be enabled as long as the iscsid.socket *is* enabled. If this base-level socket is enabled then systemd takes care of starting the iscsid service (and accompanying daemon) when needed. This means that if no iscsid service is being used that the iscsid daemon is never started. This is why the iscsid.socket service should be enabled by default. In addition, the new open-iscsi/systemd integration means that higher-level iscsi services, such as logging into (or out of) targets, thus establishing sessions, is now layered as an additional service on top of the iscsid.service. This new top-level service is called iscsi.service, and only worries about logging into targets if (and only if) the user has those targets in their iSCSI database as needing to be connect at boot time. This new iscsi.service service has no associated daemon, and will only activate the iscsi.service iscsid daemon if needed. Again, no load on the end-user's system. And I would argue that if the user has iscsi nodes in their database that are listed as needing to be connect "onboot", that we had better have that service enabled, or the user is not going to have a good boot experience. Again, the systemd units iscsid.socket and iscsi.service need to be enabled by default. -- 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.