selftest: re-enable nss_winbind via nss_wrapper in the test-envs.

Volker Lendecke Volker.Lendecke at SerNet.DE
Thu Feb 19 03:41:33 MST 2015

On Thu, Feb 19, 2015 at 11:34:59AM +0100, Stefan (metze) Metzmacher wrote:
> Am 19.02.2015 um 11:13 schrieb Volker Lendecke:
> > On Thu, Feb 19, 2015 at 11:06:36AM +1300, Andrew Bartlett wrote:
> >>> Maybe this is just
> >>> not true with the way smbd is used in the DC environment, but
> >>> I was not aware. That is the basis of my statement that I
> >>> consider a DC setup without nss_winbind incomplete, or broken. :)
> >>
> >> OK.  But given that isn't the case, you might now understand my concern
> >> with your change.
> > 
> > Andrew, is it possible that you are talking about the ntvfs server? I can
> > well believe that ntvfs does not do nss calls, smbd clearly does. Winbind
> > is required to serve AD with smbd, and thus is nss_winbind. Any support
> > question about this I would reject as WONTFIX.
> > 
> > If you have legacy ntfs/winbind4 installations, the situation might be
> > different, but if we run smbd in any DC test environment, nss_winbind
> > is mandatory.
> Currently nss_winbind is not required for smbd on a domain controller,
> all testing I've done yet was without it (I tested with the source4/winbindd
> on 4.0/4.1 and the source3/winbindd on master).

smbd does not do any nss calls on a DC at all? Wow, I did
not know that. Thanks for the update.


SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen, mailto:kontakt at

More information about the samba-technical mailing list