[Trac #1242] Web fails to launch in build 368 if DNS servers cannot be reached
Zarro Boogs per Child
bugtracker at laptop.org
Sun Apr 1 21:04:38 EDT 2007
#1242: Web fails to launch in build 368 if DNS servers cannot be reached
-------------------------+--------------------------------------------------
Reporter: dcbw | Owner: marco
Type: defect | Status: new
Priority: blocker | Milestone: Trial-1
Component: web browser | Keywords:
-------------------------+--------------------------------------------------
Because of Mozilla's profile directory locking, which depends on
gethostbyname(), Web gets a SIGKILL from somewhere after about 15 seconds
of not being able to resolve the local hostname.
NetworkManager in build #368 is unique-ifying the hostname, but was not
updating /etc/hosts to create the static host mapping back to 127.0.0.1.
I've modified NetworkManager to correctly update /etc/hosts when it
changes the hostname, which is what should happen, but we should also fix
Web to handle this gracefully and not die. We don't need Mozilla profile
locking on NFS at this time, which is why Mozilla does this.
--
Ticket URL: <http://dev.laptop.org/ticket/1242>
One Laptop Per Child <http://laptop.org/>
More information about the Bugs
mailing list