Possible reason for f5a0ccc228ce1ef failure

[Andrew Bartlett]

On Wed, 2016-03-23 at 09:09 +0100, Volker Lendecke wrote:
> On Wed, Mar 23, 2016 at 09:54:12AM +1300, Andrew Bartlett wrote:
> > > as a workaround, but that then also fails due to the unexpected
> > > success. This is just a very, very closely knit gordian knot that
> > > I
> > > don't really dare touching without asking. It took me three full
> > > days
> > > to find this, so I am close to just giving up and not touch
> > > idmapping
> > > again.
> > 
> > asking.  I'll look into why we have the wrong winbind path, but
> > this
> > looks like a very, very reasonable thing to do in any case.
> 
> You mean you think it's the right thing to do? Pull a gid
> from a different winbind than this is going to be used in?

No, the opposite: Separating the ranges is the right thing to do!

I'm going to look into the socket path issue, I don't know why that is
the case but I agree it is most suspicious. 

Thanks,

Andrew Bartlett

-- 
Andrew Bartlett                       http://samba.org/~abartlet/
Authentication Developer, Samba Team  http://samba.org
Samba Developer, Catalyst IT          http://catalyst.net.nz/services/samba