Bjoern Voigt wrote:
Per Jessen wrote:
Per Jessen wrote:
Bjoern Voigt wrote:
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. Um, the script you pasted earlier:
http://paste.opensuse.org/30183920
seems to be called "altairlmx_init", not "altairlmx". Which one is correct?
I have just added your script to my Leap421 test system, called it "altairlmx_init" and chmod'ed +x :
office34:/etc/init.d # systemctl status altairlmx_init altairlmx_init.service - LSB: Altair_Lmxd for Altair products Loaded: loaded (/etc/init.d/altairlmx_init) Active: inactive (dead) Thanks.
The installer installs an executable script /etc/init.d/altairlmxd: -rwxr-xr-x 1 root root 6395 Apr 26 11:53 /etc/init.d/altairlmxd
The header lines say that the script has to be called altairlmx_init, but it's only a comment which is probably not evaluated.
Ah, okay - it did seem like a stupid thing, but you never know. Well, I'm running out of thing to try - on my Leap421 test system, init scripts are picked up right away, no need to reload systemd, run systemd-sysv-convert etc. I don't understand how "systemctl status" can say # systemctl status altairlmxd ● altairlmxd.service Loaded: not-found (Reason: No such file or directory) yet you can start it with "systemctl start". /Per -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org