Re: [systemd-devel] How to handle alias and sysv init enable/disable (mariadb/mysql)
Michael Biebl , 10/11/2018 - 20:48:50 (+0100): > I updated > https://wiki.debian.org/Teams/pkg-systemd/Packaging#systemd_unit_files_naming_and_installation > a bit. Hope it's helpful. Let me know if it needs further clarifications. That seems very clear an promising. I am going to test this! Thanks ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] How to handle alias and sysv init enable/disable (mariadb/mysql)
Am Sa., 10. Nov. 2018 um 20:04 Uhr schrieb Michael Biebl : > ... in Debian, to be clear. I updated https://wiki.debian.org/Teams/pkg-systemd/Packaging#systemd_unit_files_naming_and_installation a bit. Hope it's helpful. Let me know if it needs further clarifications. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] How to handle alias and sysv init enable/disable (mariadb/mysql)
Am Sa., 10. Nov. 2018 um 19:59 Uhr schrieb Michael Biebl : > > Am Sa., 10. Nov. 2018 um 19:56 Uhr schrieb Michael Biebl : > > > > My recommendation would be, to not create the myslq(d).service alias > > dynamically via > > [Install] > > Alias=mysql.service > > Alias=mysqld.service > > > > but ship it as a static symlink in the package > > As an example: > Historically, the init script for NetworkManager has been called > /etc/init.d/network-manager but I decided to keep the upstream name ... in Debian, to be clear. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] How to handle alias and sysv init enable/disable (mariadb/mysql)
Am Sa., 10. Nov. 2018 um 19:56 Uhr schrieb Michael Biebl : > > My recommendation would be, to not create the myslq(d).service alias > dynamically via > [Install] > Alias=mysql.service > Alias=mysqld.service > > but ship it as a static symlink in the package As an example: Historically, the init script for NetworkManager has been called /etc/init.d/network-manager but I decided to keep the upstream name NetworkManager.service for the systemd .service unit. Which is why I ship ls -al /lib/systemd/system/network-manager.service lrwxrwxrwx 1 root root 22 Nov 5 16:05 /lib/systemd/system/network-manager.service -> NetworkManager.service in the network-manager package. This way, I always have the proper mapping between the legacy init script and the service file. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] How to handle alias and sysv init enable/disable (mariadb/mysql)
Am Sa., 10. Nov. 2018 um 19:53 Uhr schrieb Faustin Lammler : > > Hi, > sorry if this was already discussed but I can't find any > pointer or documentation on how to handle this. > > This is the problem we are facing: > https://jira.mariadb.org/browse/MDEV-15526 > > It can be reproduced on Debian stretch by disabling mariadb service > using 'systemctl disable mariadb' (all versions of mariadb are > concerned). > > The problem is that this doesn't call the systemd-sysv-install script > (to update /etc/init.d/rc?.d links) because there is no > '/etc/init.d/mariadb' script but '/etc/init.d/mysql'. And on reboot > mariadb is not disabled because it is started by '/etc/init.d/mysql' > script. > > Of course calling 'systemctl disable mysql' does the job but we need > both command acting the same way (mysql|mariadb). > > If you have any pointer/documentation or you know a similar project - > that needs to maintain multiple name/alias for the same service - that > would be a great help. My recommendation would be, to not create the myslq(d).service alias dynamically via [Install] Alias=mysql.service Alias=mysqld.service but ship it as a static symlink in the package -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] How to handle alias and sysv init enable/disable (mariadb/mysql)
Hi, sorry if this was already discussed but I can't find any pointer or documentation on how to handle this. This is the problem we are facing: https://jira.mariadb.org/browse/MDEV-15526 It can be reproduced on Debian stretch by disabling mariadb service using 'systemctl disable mariadb' (all versions of mariadb are concerned). The problem is that this doesn't call the systemd-sysv-install script (to update /etc/init.d/rc?.d links) because there is no '/etc/init.d/mariadb' script but '/etc/init.d/mysql'. And on reboot mariadb is not disabled because it is started by '/etc/init.d/mysql' script. Of course calling 'systemctl disable mysql' does the job but we need both command acting the same way (mysql|mariadb). If you have any pointer/documentation or you know a similar project - that needs to maintain multiple name/alias for the same service - that would be a great help. Thanks! Faustin ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
