I think it's worth noting that a great deal of confusion surrounding aiccu restarts is probably related to inconsistencies in the daemon's behavior.
When the daemon starts, it will terminate if it cannot contact the tunneling service, which is very different from how the daemon behaves once it's started, where it is supposed to handle network outages gracefully, without a restart. This bug report contains logs that illustrate the behavior: https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/223825. The same behavior is present on my system running a fully patched Ubuntu 12.04 release. These inconsistencies will lead to behavior that I consider incorrect when a system boots up without network connectivity and later establishes a connection (e.g. booting a laptop while outside of wireless coverage, and later coming into range). Neither aiccu's built- in behavior or the Upstart script will handle such a scenario correctly (recall the Upstart script looks for the local-file-system signal in addition to the net-device-up signal). Seems to me the best solution to these issues is for the aiccu daemon to behave the same way on startup and while running. Given the choice, I'd vote for handling network outages gracefully in both scenarios: this makes the startup scripting very simple: start aiccu on boot, and let it handle everything from there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058883 Title: start-on conditions in Upstart script prevent aiccu from restarting during resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1058883/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
