[Bug 1828883] Re: systemd sysv-compatibility eats exit codes
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 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
[Bug 1828883] Re: systemd sysv-compatibility eats exit codes
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
[Bug 1828883] [NEW] systemd sysv-compatibility eats exit codes
Public bug reported: Systemd properly honors an exit code of 6 when creating a native service, like so: ---8<--- ranger@carolina:/lib/systemd/system$ cat exitcode.service [Unit] Description=Test Exit Code (Systemd) [Service] Type=oneshot ExecStart=/bin/bash -c 'exit 6' [Install] WantedBy=default.target ranger@carolina:/lib/systemd/system$ sudo systemctl start exitcode Job for exitcode.service failed because the control process exited with error code. See "systemctl status exitcode.service" and "journalctl -xe" for details. ranger@carolina:/lib/systemd/system$ echo $? 1 ---8<--- However, the equivalent SysV init file improperly returns an exit code of 0 when starting under the compatibility layer: ---8<--- ranger@carolina:/etc/init.d$ cat exitcode #! /bin/sh ### BEGIN INIT INFO # Provides: exitcode # Required-Start:$local_fs # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Test Exit Code (SysV) # Description: Test case for Systemd SysV compatibility layer ### END INIT INFO exit 6 ranger@carolina:/etc/init.d$ sudo systemctl enable exitcode exitcode.service is not a native service, redirecting to systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable exitcode ranger@carolina:/etc/init.d$ sudo systemctl start exitcode ranger@carolina:/etc/init.d$ echo $? 0 ---8<--- Even if I change the script to do `exit 1` it still returns exit code 0. These are tiny examples but we are hitting it in the real world with the startup scripts for the OpenNMS Debian/Ubuntu packages, which return exit code 6 (LSB "not configured") when there are leftover upgrade files in `/etc/opennms`. The OpenNMS startup is not properly failing on attempted startup in this case. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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
[Bug 262650] Re: resolvconf should not use dns info for interfaces that are down
someone has to do a check, because there are times that the cleanup will not happen. if vpnc gets a kill -9, it can't cleanup and it would be difficult to argue that that is a bug with vpnc. there is a convention as you mention. if resolveconf enforced it, others would follow it. for that matter they already do seem to follow it. in the end you can point the fingers how ever you want, but this problem is easy to address in a general way in resolvconf and is hard to address (and impossible to address in general) at the interface side. this bug results in a really horrible user experience. it should be fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/262650 Title: resolvconf should not use dns info for interfaces that are down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/262650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 410124] Re: Kubuntu 9.04 doesn't connect to any wireless network
i also had a problem with this in karmic koala. i switch to wicd and everything works fantastic! -- Kubuntu 9.04 doesn't connect to any wireless network https://bugs.launchpad.net/bugs/410124 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-network-manager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 262650] Re: resolvconf should not use dns info for interfaces that are down
is there anyway to inspire action on this bug? it is still happening and it is super annoying! -- resolvconf should not use dns info for interfaces that are down https://bugs.launchpad.net/bugs/262650 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 262650] Re: resolvconf should not use dns info for interfaces that are down
** Attachment added: "Only return interfaces that are up" http://launchpadlibrarian.net/17156898/list-records.patch -- resolvconf should not use dns info for interfaces that are down https://bugs.launchpad.net/bugs/262650 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 262650] [NEW] resolvconf should not use dns info for interfaces that are down
Public bug reported: Binary package hint: resolvconf Description:Ubuntu 8.04.1 Release:8.04 resolvconf:1.38ubuntu1 When resolvconf merges the dns information that it has collected to build a new resolv.conf, it should skip information from any interfaces that are down. I'm running into this problem because vpnc doesn't seem to be cleaning up its information when it dies abnormally, so its invalid information says in resolv.conf. I think the problem is in list-records. It returns a list of interfaces for which there is dns information. I think it should return a list of interfaces for which there is dns information AND that interface is up. The attached patch does this. ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New -- resolvconf should not use dns info for interfaces that are down https://bugs.launchpad.net/bugs/262650 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60079] Re: "shopt" xsession error upon login
attached is my /etc/profile ** Attachment added: "/etc/profile" http://librarian.launchpad.net/6339021/profile -- "shopt" xsession error upon login https://launchpad.net/bugs/60079 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60079] Re: "shopt" xsession error upon login
nope, I didn't edit /etc/profile, nor do I have a ~/.profile file, only ~/.bashrc looking at it closely, it's the one from /etc/skel/.bashrc with a few aliases and env vars added, and a "set -o vi" I can't imagine that would trigger bash-specific behavior, but I dunno... -- "shopt" xsession error upon login https://launchpad.net/bugs/60079 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60079] Re: "shopt" xsession error upon login
How would I go about figuring out what session I've got? When I'm in gdm, it just says "last session" and an ls -la in my home dir doesn't give me anything with "session" in the name. I'm starting up in gnome, if that's what you're referring to. -- "shopt" xsession error upon login https://launchpad.net/bugs/60079 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60079] "shopt" xsession error upon login
Public bug reported: Binary package hint: gdm I'm not sure if this is a gdm issue, or a bash issue, but the current /etc/skel/.bashrc has a call to "shopt" which causes my login to fail. I just upgraded to edgy from dapper with a dist-upgrade, and when I try to log in, I get the following error: /etc/gdm/PreSession/Default: Registering your session /etc/gdm/PreSession/Default: running: /usr/X11R6/bin/sess /etc/gdm/Xsession: Beginning session setup... /home/ranger/.bashrc: 13: shopt: not found /etc/bash_completion: 44: Syntax error: Bad substitution This appears to be a problem with bash3 being more anal than bash2 about POSIX shell compatibility when called as /bin/sh. If I change /etc/gdm/Xsession to have "#!/bin/bash" instead of "#!/bin/sh" the error goes away. either the skel files and bash_completion (at least) need to remove their bash-isms (which is rather silly since they're provided by bash and bash_completion respectively), or Xsession needs to use bash instead of sh. ** Affects: gdm (Ubuntu) Importance: Untriaged Status: Unconfirmed -- "shopt" xsession error upon login https://launchpad.net/bugs/60079 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
