My second test did not fare so well. Even with sysvinit, there seems to be a race condition with samba.
I believe the right course it to put logic into the startup script to wait for the network. In my first test case, spanning-tree portfast was set on the switch in question, which leads to faster negotiation times at layer 2 on the network.
My second test case did a full auto-negotiate, leading me to believe that having samba wait for network state may be the right thing to do.
My second test did not fare so well. Even with sysvinit, there seems to be a race condition with samba.
I believe the right course it to put logic into the startup script to wait for the network. In my first test case, spanning-tree portfast was set on the switch in question, which leads to faster negotiation times at layer 2 on the network.
My second test case did a full auto-negotiate, leading me to believe that having samba wait for network state may be the right thing to do.