Comment 13 for bug 1058883
Revision history for this message
| Jeroen Massar (massar) wrote Re: start-on conditions in Upstart script prevent aiccu from restarting during resume from suspend | #13 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
> When the daemon starts, it will terminate if it cannot contact the tunneling service
At failures it will always log the error and terminate. This as that is the way that a user will notice things and start looking into logs. Unfortunately people seem to think that everything needs the Win95 treatment and just restart things instead.
>, 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.
That is correct, but how is that inconsistent?
> This bug report contains logs that illustrate the behavior: https:/
> The same behavior is present on my system running a fully patched Ubuntu 12.04 release.
That shows as the first line indicates that somebody decided to change the startup method which then caused things to break as there was no network yet. Simple solution: start it (once, btw, and not repeatedly) when your network connectivity is up.
> These inconsistencies
That is not inconsistent. If there is an error condition (broken time, no network) it exits.
Now, if your IP address changes while it is already running, then it will keep on working.
> Neither aiccu's built-in behavior or the Upstart
Please note that Upstart is something from Ubuntu etc, do not start blaming AICCU for the way that that start script handles it.
> (recall the Upstart script looks for the local-file-system signal in addition to the net-device-up signal).
Then fix upstart.
> Seems to me the best solution to these issues is for the aiccu daemon to behave the same way on startup and while running.
As it retrieves it's primary configuration details using TIC, it needs them, in it's current incarnation it will thus properly exit.
> 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.
This is what will be likely the case in the next AICCU version, which I want to finish but do not get around to unfortunately, maybe tomorrow will be the right day though....