summaryrefslogtreecommitdiff
path: root/source3/winbindd
diff options
context:
space:
mode:
authorMatthias Dieter Wallnöfer <mwallnoefer@yahoo.de>2009-10-06 19:27:17 +0200
committerMatthias Dieter Wallnöfer <mwallnoefer@yahoo.de>2009-10-06 19:41:16 +0200
commit8536e1b947ad8a2bc5596a9a1de9a58262153ebf (patch)
treefaac1f52c49a524211f8f80c56f525741c3b54e2 /source3/winbindd
parent0d7c34a5b4362ae8b1083a8bcf3a4115c37cafde (diff)
downloadsamba-8536e1b947ad8a2bc5596a9a1de9a58262153ebf.tar.gz
samba-8536e1b947ad8a2bc5596a9a1de9a58262153ebf.tar.bz2
samba-8536e1b947ad8a2bc5596a9a1de9a58262153ebf.zip
s4:various LDB modules - "build_request" functions - propagate result codes back
It's very useful to know the exact result code when something fails and not only a generic (by the module) created one. Sure, there are some exception cases with specific results (special message constellations, attributes, values...) which shouldn't be changed at all (examples of them are in the "ldap.py" test). Therefore I looked very carefully to not change them.
Diffstat (limited to 'source3/winbindd')
0 files changed, 0 insertions, 0 deletions