Unfortunately, you can't check if dhclient has done the Right Thing, since it daemonizes, and stays put in the background. The value of 150ms was picked since there was a call to usleep in the code that specified it, and I shifted it to be called just after dhclient. I see your point, perhaps a loop that checks if an IP has been assigned, sleeping for 100ms, and dropping out and screaming after 5 seconds?
Simon,
Unfortunately, you can't check if dhclient has done the Right Thing, since it daemonizes, and stays put in the background. The value of 150ms was picked since there was a call to usleep in the code that specified it, and I shifted it to be called just after dhclient. I see your point, perhaps a loop that checks if an IP has been assigned, sleeping for 100ms, and dropping out and screaming after 5 seconds?