On 10/23/2013 08:38 PM, Cristian Rodríguez wrote:
El 23/10/13 15:10, Lee Duncan escribió:
- At the lowest level is the unit iscsid.socket - The iscsid.service unit is tied to the iscsid.socket unit, and - The iscsi.service unit
Ok, I assume before doing that you explored what others did in different distributions and you did not invented your own way...
Question 1: What is the best way to ensure these units get enabled correctly, i.e. iscsid.socket and iscsi.service enabled and iscsid.service not enabled? I tried to ensure that this package got installed correctly by enabling the iscsid.socket and iscsi.service units automatically upon installation, but it looks like there is an openSUSE policy to not enable any service by default. There also seems to be exceptions, but both the reasons behind the policy and the exceptions to that policy do not seem documented.
You have to open a request for the services to be added to the "preset" packages.. this is the way to enable services by default.
He did that - and that's why I send him here. Since we do not want to have every package enable every service when it gets installed, we have a whitelist of services to start. It's not clear yet to me whether we should make an exception for iscsid like he requests. I need to reread Lee's nice summary another time to chime in, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org