tdb2/ntdb means that tdb_inc_seqnum can't be use directly

Rusty Russell rusty at
Wed Jun 13 01:01:01 MDT 2012

On Wed, 23 May 2012 21:20:58 -0700, Matthieu Patou <mat at> wrote:
> On 05/23/2012 05:55 PM, Rusty Russell wrote:
> > On Wed, 23 May 2012 00:57:13 -0700, Matthieu Patou<mat at>  wrote:
> >> Hello Rusty,
> >>
> >> I was trying to use tbd_inc_seqnum and realized that write operation in
> >> tdb2 are using it also so it's not a good idea for me to use it tdb2/ntdb.
> > I don't understand.  Writes in tdb1 used it too...
> Oh right, I thought it wasn't.
> >
> > It's not exposed, because noone needed it.  Why do you want to use it?
> Well for schema update I need process A to tell process B I have 
> reloaded the schema because I had too or I was asked so should you.
> I was suggested to use tdb_inc_seqnum and tdb_get_seqnum as I don't need 
> to have an exact value but just the info that something has changed and 
> that schema has to be reloaded.
> So it wouldn't be too bad to be able to use tdb_inc_seqnum (ldb seems to 
> call it directly).

Hmm, ldb doesn't call it directly in my tree: can you point out where?

Any change to the database will update it, as Volker said.


More information about the samba-technical mailing list