On Tue, Mar 3, 2009 at 10:12 PM, Mike Telahun Makonnen <mmakonnen_at_gmail.com> wrote: > On Tue, Mar 3, 2009 at 9:03 PM, Brooks Davis <brooks_at_freebsd.org> wrote: >> >> I don't have much time to debug this, but I've not had problems with >> services starting too early on the systems I've been running with async >> dhcp. If there is a problem with the wait process we need to actually >> debug it. If the wait for a route/running interface isn't sufficent we >> should try to figure out what is. Synchronous dhcp sucks and yeilds >> justifed user complaints so it would be nice to kill it off. I switched >> the default because it worked for me and I hoped that people would help >> find and fix edge cases. > > Can you elaborate why synchronous DHCP sucks ? The only reason I could see is bringup time. Am I correct in this assumption? >> >> BTW, the change to background by default still doesn't make sense to >> me. At best it shouldn't do anything useful in the async case and it >> entierly defeats the sync case. >> > > Yeah, I realized this as soon as people started complaining about the > changes and reverting that commit didn't fix their problem. I'll back > it out. Thanks :), -GarrettReceived on Wed Mar 04 2009 - 07:04:07 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:43 UTC