lpdap rebind sleep

[Stefan (metze) Metzmacher]

At 01:25 25.10.2002 +1000, Andrew Bartlett wrote:
>"Stefan (metze) Metzmacher" wrote:
> >
> > At 00:56 25.10.2002 +1000, Andrew Bartlett wrote:
> > >"Stefan (metze) Metzmacher" wrote:
> > > >
> > > > At 00:26 25.10.2002 +1000, Andrew Bartlett wrote:
> > > > >"Stefan (metze) Metzmacher" wrote:
> > > > > >
> > > > > > Hi Andrew,
> > > > > >
> > > > > > I want to add a new parameter 'ldap rebind timeout'
> > > > > >
> > > > > > I have problems when my samba adds a user following an update 
> referral.
> > > > > > samba tries to read the new entry to verify that it now exist. 
> but the
> > > > > > replication to the read-only server isn't so fast so the new
> > > account can't
> > > > > > be found. to avoid this I preferr a 
> msleep(lp_ldap_rebind_timeout()),
> > > > > > default 1500 = 1,5 s
> > > > >
> > > > >Hmm...  I really hope there is a more elegent way to deal with this...
> > > >
> > > > tell me one
> > >
> > >Well, it might be somthing we need to leave till the SAM,
> >
> > No, if we support rebinding at all it must work in 3_0!
> >
> > >  but why do we
> > >re-read?
> >
> > we didn't reread the entry directly
>
>Actually, we do...  See the end of the createuser RPC.
>
> >, but when we do a domain join from NT
> > it add's the account and reread it to verify that it's successful added or
> > whatever MS tries to there...
> >
> > >  An arbitary sleep just seems like the wrong idea.  Or better
> > >to sleep until our mirror catches up, not just 1.5 seconds.
> >
> > hmm don't know... I know use the msleep(2000) in my servers.
> >
> > good ideas are very wellcome here...
>
>After an add, we could sit in a loop doing a 'get', until the response
>appears.  (Sleep/retry loop).

sounds good....



metze
-----------------------------------------------------------------------------
Stefan "metze" Metzmacher <metze at metzemix.de>