For whatever reason the conditions were not met for it to run that particular code where it would iterate through all the available interfaces. It kept trying to run ipconfig on the first interface with the link and get stuck there.
Now, we have a number of machines with 12 interfaces and even if it did iterate through all the interfaces, going through 12 is quite slow as you can imagine, it takes 15 seconds to go through one interface. Rather then spending time on figuring out why the conditions weren't met to go through that code, I wrote another solution which would depend on bootif, which is much faster. To answer your question, I frankly don't know On Sep 4, 2011 12:38 PM, "Joseph Gunn" <[email protected]> wrote: > On Sun, 4 Sep 2011 12:00:17 -0700 > Kash <[email protected]> wrote: > >> Actually I removed it because it was not needed for our environment and if >> you read the previous discussion I mentioned that this is a working code for >> bootif only. Regardless, I'll send in another patch, adding in the code that >> I removed, and it will fall back to it in case bootif is not available. > Not really my call. i am working on a setup to reproduce the issue either way. > > I should be able to understand why the old code fails at least.
