omninames and nodebooter take 100% CPU during device startup

[balister]

Omninames and nodebooter are taking 100% CPU during startup on a small form factor system.

I believe this is similar to a problem fixed during component startup where the framework polls omniNames to see when a device has started. On a high speed desktop, this is not noticeable, but on small systems the system spends so much time looking for the name, the device takes a long time to start up.

The (quick) solution is find the code in the device manager that starts the devices and insert a short sleep in the loop.

[balister]

I thought we had fixed component startup in the application factory also, but I am seeing the same problem there.

Review both device manager and application factory code for checking that a component has started.

[balister]

Further inspection of the code show the time delays are in both places, however the values appear to be small for the hardware I am working with. I am going to change the time delay so that it increases by a factor of two each time through the loop. Hopefully, this stops small machines from beating themselves to death while still letting fast machines start up quickly.

[balister]

r6471 did not appear helpful. Grrr.