<div dir="ltr">macs are right. Sometimes it come back, sometimes it doesn't. I'll try and google the linux network auto process dependencies. Sure seems really unpredictable<br></div><div class="gmail_extra"><br>
<br><div class="gmail_quote">On Tue, Nov 12, 2013 at 12:06 PM, Michael J. Hammel <span dir="ltr"><<a href="mailto:mjhammel@graphics-muse.org" target="_blank">mjhammel@graphics-muse.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Tue, 2013-11-12 at 10:51 -0700, Mike Bean wrote:<br>
> anything that I recognize, but the only logical option that makes any<br>
> sense at all, is that whatever process RHEL uses to start/configure<br>
> the network without manual intervention is broken somehow.<br>
<br>
</div>WAG: manual run is post-init processes (systemd). Auto run is while<br>
init processes are running. Therefore, auto process is hung waiting on<br>
some other init process while manual process doesn't have to wait on<br>
that. The auto process waits and never gets notified that what its<br>
waiting on has completed (or perhaps the waiting prevents it from<br>
completing). The auto process has a chicken-n-egg problem.<br>
<br>
Question is: what is network startup waiting on during init process?<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Michael J. Hammel <<a href="mailto:mjhammel@graphics-muse.org">mjhammel@graphics-muse.org</a>><br>
<br>
_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br>
</font></span></blockquote></div><br></div>