By default, dhcpxd forks itself in the background, even before the configuration is done. This:
1) doesn\'t play good with initlog -- dhcpxd appears to block on output;
2) doesn\'t fit into the service startup model -- the ifup script should not return until the interface is either configured, or failed to configure.Fortunately, there is -w option that prevents dhcpxd from forking. The timeout in case of dead Ethernet is not prolonged, so I think it should be OK to wait for a while.
A patch is provided for clarity.
---

---