John Andersen wrote:
On April 25, 2016 11:16:40 PM PDT, Per Jessen <per@computer.org> wrote:
John Andersen wrote:
On 04/25/2016 02:18 PM, Per Jessen wrote:
John Andersen wrote:
On 04/25/2016 01:26 PM, Bjoern Voigt wrote:
The service now starts automatically after calling once:
systemd-sysv-convert --save altairlmxd
I do not exactly know, why this is necessary.
It is necessary because Altair hasn't yet recognized that the entire world has gone Systemd. Even the Raspberry Pi linux distro now uses systemd.
Altair is too lazy to revise their packages to operate correctly in the modern world (except for those few distros that are hold-outs). You should file a bug report with them.
At most a feature request - systemd provides sysvinit compatibility, LSB init scripts should continue to work.
Apparently not. At least not unless you remember to runs some relatively obscure command after install, which should be done by the Altair installer.
If anything, systemd-sysv-convert should be invoked automagically, but I'm not intimately famniliar with the process. To my knowledge there is no conversion "needed", LSB init scripts are supported as they are.
Once again I say, Apparently not. Because it didn't work "as they are" for the OP.
Right, but we don't who is to blame, the init script, systemd or the OP.
And the solution is for Altair to fix their install process, to either work with existing unit scripts or add the systems targets. Or both.
According to what Björn posted, the init script worked before the update, and the diff shows no significant changes. Anyway, Björn wanted to know how to debug this - "systemctl status service" will tell you how systemd sees things. That ought to be a good place to start. -- Per Jessen, Zürich (9.1°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org