[yast-devel] systemd & installation
As in the foreseeable future there will be no systemd running during installation (systemd does not work for PID != 1) and the old init.d scripts are gone I've added a 'service_start' script to the installation system. So, if you really have to start service 'foo' for some reason, try 'service_start foo'. It's far from perfect but I hope it works at least for the most common services. Steffen -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 19.3.2014 11:15, Steffen Winterfeldt wrote:
As in the foreseeable future there will be no systemd running during installation (systemd does not work for PID != 1) and the old init.d scripts are gone I've added a 'service_start' script to the installation system.
So, if you really have to start service 'foo' for some reason, try 'service_start foo'.
It's far from perfect but I hope it works at least for the most common services.
Thanks Steffen, So, does it mean we should change the Service.rb to use `service_start` instead of `systemctl` during (first stage) installation? Is there a `service_stop` command? Vlado, would you have a look, please? Thanks Lukas -- Lukas Ocilka, Yast TL, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Thu, 20 Mar 2014, Lukas Ocilka wrote:
On 19.3.2014 11:15, Steffen Winterfeldt wrote:
As in the foreseeable future there will be no systemd running during installation (systemd does not work for PID != 1) and the old init.d scripts are gone I've added a 'service_start' script to the installation system.
So, if you really have to start service 'foo' for some reason, try 'service_start foo'.
It's far from perfect but I hope it works at least for the most common services.
Thanks Steffen,
So, does it mean we should change the Service.rb to use `service_start` instead of `systemctl` during (first stage) installation? Is there a
Yes. systemctl just doesn't work.
`service_stop` command?
No. I could provide a dummy service_stop script so that if ever it would be necessary to stop a service we don't have to look at the code again. But ATM I think we're fine just rebooting. Steffen -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Hi, On 03/20/2014 10:42 AM, Lukas Ocilka wrote:
On 19.3.2014 11:15, Steffen Winterfeldt wrote:
As in the foreseeable future there will be no systemd running during installation (systemd does not work for PID != 1) and the old init.d scripts are gone I've added a 'service_start' script to the installation system.
So, if you really have to start service 'foo' for some reason, try 'service_start foo'.
It's far from perfect but I hope it works at least for the most common services.
Thanks Steffen,
So, does it mean we should change the Service.rb to use `service_start` instead of `systemctl` during (first stage) installation? Is there a `service_stop` command?
Vlado, would you have a look, please?
Yes, I will patch the Yast::Service module and I'm considering to add this also into the Yast::SystemdService to have consistent API in installation environment for both modules. Vlado -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 20.3.2014 15:31, Vladimir Moravec wrote:
So, does it mean we should change the Service.rb to use `service_start` instead of `systemctl` during (first stage) installation? Is there a `service_stop` command?
Vlado, would you have a look, please?
Yes, I will patch the Yast::Service module and I'm considering to add this also into the Yast::SystemdService to have consistent API in installation environment for both modules.
IIUC, there should be just one module to be changed and not two of them. For historical reasons we maybe have Service and SystemdService, but if we keep Service as "THE" API, then it probably just needs to call SystemdService underneath (or vice versa?). Thx Lukas -- Lukas Ocilka, Yast TL, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 03/20/2014 03:38 PM, Lukas Ocilka wrote:
On 20.3.2014 15:31, Vladimir Moravec wrote:
So, does it mean we should change the Service.rb to use `service_start` instead of `systemctl` during (first stage) installation? Is there a `service_stop` command?
Vlado, would you have a look, please?
Yes, I will patch the Yast::Service module and I'm considering to add this also into the Yast::SystemdService to have consistent API in installation environment for both modules.
IIUC, there should be just one module to be changed and not two of them. For historical reasons we maybe have Service and SystemdService, but if we keep Service as "THE" API, then it probably just needs to call SystemdService underneath (or vice versa?).
I agree, but currently they are not merged and their API is different. Now it's easier to add support for inst-sys for both of them separatelly than to share the implementation of SystemdService within Service. Or if the need for starting a service in inst-sys is not that urgent, I would add it later with changing the implementation of Service at once. vlado -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 21.03.2014 08:50, schrieb Vladimir Moravec:
On 03/20/2014 03:38 PM, Lukas Ocilka wrote:
On 20.3.2014 15:31, Vladimir Moravec wrote:
So, does it mean we should change the Service.rb to use `service_start` instead of `systemctl` during (first stage) installation? Is there a `service_stop` command?
Vlado, would you have a look, please?
Yes, I will patch the Yast::Service module and I'm considering to add this also into the Yast::SystemdService to have consistent API in installation environment for both modules.
IIUC, there should be just one module to be changed and not two of them. For historical reasons we maybe have Service and SystemdService, but if we keep Service as "THE" API, then it probably just needs to call SystemdService underneath (or vice versa?).
I agree, but currently they are not merged and their API is different. Now it's easier to add support for inst-sys for both of them separatelly than to share the implementation of SystemdService within Service.
Or if the need for starting a service in inst-sys is not that urgent, I would add it later with changing the implementation of Service at once.
It's required and urgent for iSCSI client and FCoE client. These modules run during installation and need running services in inst-sys. Gabi
vlado
- -- Gabriele Mohr SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstr. 5 Tel: +49 911 740 53 362 90409 Nürnberg Email: gs@suse.de - ----------------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iD8DBQFTK/XuzwhO63ql6h0RAgRCAJ40BE/nhr2CRlVl795KN5QQtWGnOwCgjCrY 4WdZV8WMdITnzQcdKbOW0es= =W2e3 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/21/2014 09:18 AM, Gabriele Mohr wrote:
Am 21.03.2014 08:50, schrieb Vladimir Moravec:
On 03/20/2014 03:38 PM, Lukas Ocilka wrote:
On 20.3.2014 15:31, Vladimir Moravec wrote:
So, does it mean we should change the Service.rb to use `service_start` instead of `systemctl` during (first stage) installation? Is there a `service_stop` command?
Vlado, would you have a look, please?
Yes, I will patch the Yast::Service module and I'm considering to add this also into the Yast::SystemdService to have consistent API in installation environment for both modules.
IIUC, there should be just one module to be changed and not two of them. For historical reasons we maybe have Service and SystemdService, but if we keep Service as "THE" API, then it probably just needs to call SystemdService underneath (or vice versa?).
I agree, but currently they are not merged and their API is different. Now it's easier to add support for inst-sys for both of them separatelly than to share the implementation of SystemdService within Service.
Or if the need for starting a service in inst-sys is not that urgent, I would add it later with changing the implementation of Service at once.
It's required and urgent for iSCSI client and FCoE client. These modules run during installation and need running services in inst-sys.
I added support for the /bin/service_start script in inst-sys [1], please review and comment. [1] https://github.com/yast/yast-yast2/pull/190 Vlado -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTLBLwAAoJEK0W0ULJ7Ug//0UQAKfIm/+vE5ohlyoSWflRRkOb 3aPgZKQ8gOJNF5s9DLZAcXLsE8zCKBw+D7hXaxc9fnS2O+AziSwAR+o2hycFW3xY AefzkCeFbtcgGvw0WHjSbkIZUK2kK0Nfir0fA2aQXSSxjdE+8RqT57W4aMFvXRLT 78d7VOGut3QPkz1SOPH5Ei8uPWBUqQGVXfIrGXeGzj0TB5TvR/+9LlhyG/KE1vss ODvJPYUiHCvCRNJenEDsCyATw/F380tq0uttPYmc63bVzVcdcGFrPPR3/qdZOWlo rHprsNAty9CLA7VKGDti4u3IM3QPky0I34CwrrytjMczc/wyqQiTvbXDtqZFIF+O n9mMhc6+i4aAr7QAY9Rb9FqWnBEUvsvUtKbeBaYMid+95C33EGgNAftoLPkkm4SI xUBuhAFVbKsSH44l8hdTCcI9b3WxD0X6W57LFkmU5YVyrLO4fbeh957omFn5ZAtA QF9dtLWsAOfkd51EVhthsExbSxYOqh+Gkp6zW/M2KwBBOEEQ5DN7g3qK4/gCbBq2 5eXy3t+dUepUZakqRyCHLqE8ag/1lXywDa0vn8ens9PaOJ5l9RU8s+fFajOTN036 5B2YSMjEkdIHMbK4VooIBwwaXQ9OSXbxpz45gYy4wb1GdjBYYxlAET/SL4piZ2iL Tfx9068z1egTbcJJuRhK =GivT -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (4)
-
Gabriele Mohr -
Lukas Ocilka -
Steffen Winterfeldt -
Vladimir Moravec