Comment 68 for bug 223825

Jeroen,

Good to know this information. I'm puzzled by AICCU's behavior of shutting down on startup if it can't retrieve TIC information, since I understand you to be saying that the program won't terminate if there's an active tunnel and the computer loses connectivity (e.g. the person leaves the range of their WiFi hotspot). What is the difference, from AICCU's perspective, between having no connectivity on startup, and losing connectivity during a program run?

At any rate, the Upstart script isn't written to terminate AICCU when a network interface is taken down. The termination conditions are entering runlevels 0 or 6 (shutdown or reboot, respectively).

I'm open to suggestions on a Internet connectivity check. Currently the only sanity check is a check to make sure the interface is not the local loopback. I don't think having a default route is a very strong guarantee of connectivity, since it's quite possible for that default route to be offline. The only strong guarantee I can imagine is pinging a PoP server, but isn't that the general purpose of the heartbeat protocol? Seems like it'd be a re-invention of the wheel.

Clint,

Thanks for the recommendation. I'm not sure about this change, though, because we don't want to start the daemon unless there's a (non-loopback) network connection present. Unless I'm badly mistaken, there's no guarantee that a network connection will be present when the system switches to runlevel 2. If so, there's a good possibility that AICCU would simply terminate on startup, as Jeroen mentions. Not the end of the world, but certainly not necessary either.