>>>> I think, this tricks with "pre-up /etc/init.d/openvswitch-switch start" >>>> and "auto" order must be documented. >>> Did you read my first email and try removing things from auto? >> >> I have checked this, but there are potential problem exist: if I remove >> ovs-controlled interfaces from auto, they will be configured only after >> openvswitch-switch start > I think, that is how it should work. OVS interfaces can only do anything > meaningful after openvswitch-switch start. >> and some daemons (which starts before openvswitch-switch, i.e. almost all >> daemons on my machine) will see no interfaces and IP addresses and may fail >> to start. > > One option is to make your other scripts depend on openvswitch-switch > > Your solution should be okay too as long as /usr is not mounted through NFS. > It is a known shortcoming because of a circular dependency.
Putting openvswitch on NFS-mounted filesystem -- very strange idea :) By the way, NFS daemons on my machine starts before ovs, I can change daemon dependency editing init-scripts, but after next upgrade init-scripts can be updated and I will get unreachable from network machine. Pavel. _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
