<html><body><div style="color:#000; background-color:#fff; font-family:lucida console, sans-serif;font-size:10pt"><div>Bug 56122: Original bug report misunderstood; root problem not corrected<br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: lucida console,sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: lucida console,sans-serif; background-color: transparent; font-style: normal;">Hint #1 is the subject of the original report:</div><div>Race condition between ntp and NetworkManager at entry to runlevel 2</div><div><br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: lucida console,sans-serif; background-color: transparent; font-style: normal;">Hint #2 from original report:</div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: lucida console,sans-serif; background-color: transparent;
font-style: normal;">Scope: The symptom I see is a problem with ntp. The underlying<br> cause could affect other network services as well.</div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: lucida console,sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: lucida console,sans-serif; background-color: transparent; font-style: normal;">Hint #3 from original report: log excerpt showing ntp trying to initialize 5 seconds before NetworkManager brings up eth0.<br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: lucida console,sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: lucida console,sans-serif; background-color: transparent; font-style: normal;">Briefly:</div><div style="color: rgb(0, 0, 0); font-size:
13.3333px; font-family: lucida console,sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: lucida console,sans-serif; background-color: transparent; font-style: normal;">As long as NetworkManager brings down the network interface and then brings it up again, all asynchronously to the startup of network services, some of those network services are <span style="font-weight: bold;">sometimes</span> going to try to initialize themselves while the network interface is down and consequently fail.</div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: lucida console,sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: lucida console,sans-serif; background-color: transparent; font-style: normal;">It is impractical to try to bulletproof every network service to deal
with the network interface being down when the service tries to start.</div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: lucida console,sans-serif; background-color: transparent; font-style: normal;"><br></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: lucida console,sans-serif; background-color: transparent; font-style: normal;"><span style="font-weight: bold;">No network service should be started until NetworkManager indicates that the network interface is up.</span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: lucida console,sans-serif; background-color: transparent; font-style: normal;"><br><span style="font-weight: bold;"></span></div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: lucida console,sans-serif; background-color: transparent; font-style: normal;"><span>I have tried to explain this as clearly as I can. I don't have the energy to rehash
it again. If whoever reads this doesn't understand what a race condition is and why Debian network startup has a race condition please kick this message upstairs. Thanks.<br></span></div><br></div></body></html>