On Wed, Apr 04, 2012 at 01:47:58PM -0700, Ethan Jackson wrote:
> > + seqno = idl.change_seqno # Sequence number when we last processed
> > the db
>
> Does it make sense to initialize seqno to None so we're guaranteed to
> run through the database initially? Looking at ovs-xapi-sync it uses
> + seqno = idl.change_seqno # Sequence number when we last processed the
> db
Does it make sense to initialize seqno to None so we're guaranteed to
run through the database initially? Looking at ovs-xapi-sync it uses
this same model, so I suspect it's fine. Just a thought, feel free to
ig
This does not fix an actual bug in ovs-monitor-ipsec because it does not
ever commit any changes to the database.
Signed-off-by: Ben Pfaff
---
debian/ovs-monitor-ipsec |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/debian/ovs-monitor-ipsec b/debian/ovs-monitor-ips
