On Mon, Mar 18, 2013 at 12:39:33PM -0700, Gurucharan Shetty wrote:
> On Mon, Mar 18, 2013 at 12:18 PM, Ben Pfaff wrote:
> > On Mon, Mar 18, 2013 at 10:48:49AM -0700, Gurucharan Shetty wrote:
> >> Previously, ovs-vsctl would wait for ever if ovsdb-server
> >> was not running. In such a situation, i
On Mon, Mar 18, 2013 at 12:18 PM, Ben Pfaff wrote:
> On Mon, Mar 18, 2013 at 10:48:49AM -0700, Gurucharan Shetty wrote:
>> Previously, ovs-vsctl would wait for ever if ovsdb-server
>> was not running. In such a situation, it made sense to use
>> a "--timeout" value to prevent a stuck startup scrip
On Mon, Mar 18, 2013 at 10:48:49AM -0700, Gurucharan Shetty wrote:
> Previously, ovs-vsctl would wait for ever if ovsdb-server
> was not running. In such a situation, it made sense to use
> a "--timeout" value to prevent a stuck startup script. But now,
> ovs-vsctl by default returns an error if ov
Previously, ovs-vsctl would wait for ever if ovsdb-server
was not running. In such a situation, it made sense to use
a "--timeout" value to prevent a stuck startup script. But now,
ovs-vsctl by default returns an error if ovsdb-server is
not running. So, we no longer need the timeout option.
Signe
