[PATCH] RFC debug detect winbindd version mismatches

Volker Lendecke Volker.Lendecke at SerNet.DE
Mon Jan 27 06:18:28 MST 2014

On Mon, Jan 27, 2014 at 07:27:34AM -0500, Jim McDonough wrote:
> On Mon, Jan 27, 2014 at 6:20 AM, Volker Lendecke
> <Volker.Lendecke at sernet.de> wrote:
> > On Mon, Jan 27, 2014 at 10:35:47AM +0000, Noel Power wrote:
> >> A simple debug related tweak that adds a new wbcError category which
> >> allows winbindd version mismatch errors to be detected/reported. Its
> >> likely one of the many wbcErrorString around the code will now print out
> >> some more useful info. Please review/push if you think it's useful
> >
> > libwbclient is supposed to be shipped with winbind, it
> > should always come in the same RPM or have a strict version
> > dependency. In what circumstances do you need better
> > diagnostics for this?
> It's not so much _needed_ as helpful.  If a loaded binary, such as
> sshd, isn't restarted, it's could be a quicker or more obvious
> indicator.  Or in the case where an administrator has done something
> unwise like manually installing binaries/moving things around.  Not
> strictly needed, but could be a time saver.
> Not worth a lot of effort/comment, but if someone else found it useful
> for their support folks (ours cover a wide range of topics) to guide
> their thinking...

I'm not opposed to this feature. Question: Is there a way to
do this without a global variable? Maybe with a special call
that queries the currently available interface version, or
some other error code? I know that NSS_STATUS is a given,
maybe we should pass something else here? Just


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
http://www.sernet.de, mailto:kontakt at sernet.de

More information about the samba-technical mailing list