Andrei Borzenkov wrote:
On Tue, Apr 26, 2016 at 1:14 PM, Per Jessen <per@computer.org> wrote:
Bjoern Voigt wrote:
Per Jessen wrote:
Per Jessen wrote:
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. for LSB services, "systemctl status" does not tell us if a service is enabled or disabled, so please also run "chkconfig altairlmxd".
Sorry, I switched from Leap 42.1 to Tumbleweed because I currently can't test the Leap 42.1 server.
They are quite different animals.
Directly after installation I have:
# systemctl status altairlmxd ● altairlmxd.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)
That's clearly not good. It ought to find your init script in /etc/init.d/altairlmxd.
No. systemd looks for unit definitions only on startup or when explicitly told to do so by "systemctl daemon-reload".
That is not my experience on Leap421. I just tried it with the altairlmx_init file - only had to edit it and chmod +x it, then: office34:~ # systemctl status altairlmx_init altairlmx_init.service - LSB: Altair_Lmxd for Altair products Loaded: loaded (/etc/init.d/altairlmx_init) Active: inactive (dead) office34:/etc/init.d # l andrei-borzenkov ls: cannot access andrei-borzenkov: No such file or directory office34:/etc/init.d # touch andrei-borzenkov office34:/etc/init.d # systemctl status andrei-borzenkov andrei-borzenkov.service Loaded: masked (/etc/init.d/andrei-borzenkov) Active: inactive (dead) -- Per Jessen, Zürich (10.3°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