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's not just that it's a "first install" situation.
Without an error exit, the user may not know that OpenNMS did not
restart properly after upgrade because there are tasks to do to have a
working OpenNMS install.
It seems strange to me that `systemd` would treat ANY error code as not-
an-error without deliberate choice from the packager's POV, but I guess
this is only one of many things that are confusing about systemd. I'll
work on making a proper systemd file for OpenNMS and then hopefully it
won't be an issue.
--
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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1828883/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
