On Thu, Jun 13, 2013 at 12:15:11PM -0700, Gurucharan Shetty wrote:
> On Thu, Jun 13, 2013 at 11:32 AM, Ben Pfaff wrote:
>
> > On Thu, Jun 13, 2013 at 11:25:07AM -0700, Gurucharan Shetty wrote:
> > > On Thu, Jun 13, 2013 at 10:29 AM, Ben Pfaff wrote:
> > > > @@ -81,8 +81,14 @@ struct add_remote_a
On Thu, Jun 13, 2013 at 11:32 AM, Ben Pfaff wrote:
> On Thu, Jun 13, 2013 at 11:25:07AM -0700, Gurucharan Shetty wrote:
> > On Thu, Jun 13, 2013 at 10:29 AM, Ben Pfaff wrote:
> > > @@ -81,8 +81,14 @@ struct add_remote_aux {
> > > struct sset *remotes;
> > > struct db *dbs;
> > > s
On Thu, Jun 13, 2013 at 11:25:07AM -0700, Gurucharan Shetty wrote:
> On Thu, Jun 13, 2013 at 10:29 AM, Ben Pfaff wrote:
> > @@ -81,8 +81,14 @@ struct add_remote_aux {
> > struct sset *remotes;
> > struct db *dbs;
> > size_t n_dbs;
> > +FILE *config_tmpfile;
> > };
> > static u
On Thu, Jun 13, 2013 at 10:29 AM, Ben Pfaff wrote:
> Commit b421d2af0ab (ovsdb-server: Add commands for adding and removing
> remotes) made it possible to make ovsdb-server connect to OVS managers only
> after ovs-vswitchd has completed its initial configuration. But this
> results in an undesir
Commit b421d2af0ab (ovsdb-server: Add commands for adding and removing
remotes) made it possible to make ovsdb-server connect to OVS managers only
after ovs-vswitchd has completed its initial configuration. But this
results in an undesirable effect: whenever ovsdb-server crashes, the
monitor resta
