** Changed in: systemd
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828883
Title:
systemd sysv-compatibility eats exit codes
To manage notifications about t
> I'll work on making a proper systemd file for OpenNMS and then hopefully
> it won't be an issue.
I think this is absolutely the best direction - if you have any
questions or problems while creating the native systemd service file,
I'm happy to help.
** Also affects: systemd via
https://githu
I have filed an issue with upstream Systemd:
https://github.com/systemd/systemd/issues/12580
** Bug watch added: github.com/systemd/systemd/issues #12580
https://github.com/systemd/systemd/issues/12580
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
I am the maintainer of the OpenNMS scripts (and debian/ubuntu packages).
We return 6 ("not configured") if there are `dpkg-dist` files that have
not been merged before startup, or if the database has not been properly
initialized. This can happen *after* upgrade of a normal working
system, so it'
All sysv service scripts (i.e. /etc/init.d/ scripts) are converted at
runtime into systemd service scripts by the systemd-sysv-generator
script; you can find them in /run/systemd/generator*/ directories.
The systemd-sysv-generator script normally does handle sysv script non-
zero exit codes as an
I've verified this on Ubuntu 18.04 LTS
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename: bionic
root@ubuntu:/etc/init.d# systemctl start exitcode
root@ubuntu:/etc/init.d# echo $?
0
root@ubuntu:/etc/init.d#
