No Internet in container bug fixed

I received feedback that when click on the "www" SeaMonkey-in-container icon, a message appears "No Internet in container" and SeaMonkey startup is aborted.

This check was introduced as SM was found to be very slow to start and unstable if started in a container without Internet access. The conjecture was that SM does some kind of network check at startup, and being inside a container must be an odd situation that confuses SM.

In the "www" container, /usr/bin/seamonkey is a script, that calls /usr/local/easy_containers/internet-container-abort. The latter calls 'getlocalip' to check for network connectivity.

I fixed the script. What I found is that 'getlocalip' is being called too soon. It takes awhile for the dhcp client to obtain an address inside the container, 5 seconds on my PC. So I put in a loop, timing out at 9 seconds. 

Yay, another one bites the dust! 

Tags: easy