https://bugzilla.novell.com/show_bug.cgi?id=846945 https://bugzilla.novell.com/show_bug.cgi?id=846945#c4 Andreas Jaeger <aj@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|aj@suse.com | --- Comment #4 from Andreas Jaeger <aj@suse.com> 2013-10-23 07:48:19 UTC --- (In reply to comment #3)
Andreas: I'm not clear on this new policy. Is it that no service is enabled by default, ever, from now on, or are there exceptions? I assumed the policy was designed to stop all services from enabling themselves by default, when installed, since that might not be what the user wanted in all cases. Especially if such automatic enablement means the system is bogged down using unneeded resources because daemons are running when not needed.
The file default-openSUSE.preset defines what is enabled by default - those are the exceptions. If there are really valid reasons to enable open-iscsi, we can add it.
In this case, it seems like the socket-driven model available to systemd services means that "enabling" iscsid.socket in this case causes almost no system impact. And I feel that the principle of least surprise should be that if the customer installs open-iscsi and runs "iscsiadm -m discovery ..." to find some nodes, they don't expect a message saying "the daemon is not running". The daemon should be started. In the System V Init days, there was a line in /etc/iscsi/iscsid.conf that told the open-iscsi system to start up the daemon in such cases, if needed. But that line has been removed because of systemd's socket-driven functionality.
I noticed that there are more than a few other services that are enabled by default, hence my confusion. Is this new policy from systemd or by openSUSE?
This is an openSUSE policy.
you have a reference to it and other such policies, so I can provide appropriate submissions in the future?
This should be documented in the openSUSE wiki under packaging guide lines but sometimes the sections are not complete.
I take it, then, that the expected work flow for most service installations will be, from the end user point of view: 1. install the service (using zypper or yast2), then 2. manually run "systemctl enable <SERVICE>" from the command line
Is this correct? In the case of open-iscsi, there are 3 services, and only 2 of
Yes, that's correct.
them should be enabled, since enabling the 3rd will mean the iscsid daemon is running even if not needed. I thought automatically installing open-iscsi with the correct 2 of 3 units enabled would result in the least number of bugs filed.
So, it's the choice of enabling two for everybody that installs it - versus the fear that users might start all three manually? Two bad choices ;( Btw. if you disagree, feel free to discuss on openstack-packaging in a larger round. -- 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.