summaryrefslogtreecommitdiff
path: root/source3/stf/osver.py
diff options
context:
space:
mode:
authorAndrew Bartlett <abartlet@samba.org>2004-05-28 08:57:00 +0000
committerGerald (Jerry) Carter <jerry@samba.org>2007-10-10 10:51:50 -0500
commitfe8977e12c5b01f9adc8df6b07d91131bd4f7432 (patch)
treed21c203ef5c10dadb295b93753e4a918e5ee33d7 /source3/stf/osver.py
parentcb03592c067a8e475a5f96f72aa0e84ba176a747 (diff)
downloadsamba-fe8977e12c5b01f9adc8df6b07d91131bd4f7432.tar.gz
samba-fe8977e12c5b01f9adc8df6b07d91131bd4f7432.tar.bz2
samba-fe8977e12c5b01f9adc8df6b07d91131bd4f7432.zip
r936: Fix a rather weird error that crippled my site, when we upgraded to
Samba 3.0.4. If we fail a query for the members of the 'administrators' group (and we may well just have the IDL wrong), this destroys later parts of the domain logon process. For reasons I can't understand, the client-side 'heck, what happened' bailout causes the connection to the DC to be dropped, and causes the mandetory profile not to be loaded. (This also only occours after a reboot) Return the members of 'administrators', and it all works fine. The reason we hit this is because we run winbindd (to support pam_winbind) on our DC, and the winbindd lookup in sid_to_gid was messing things up. As we don't care what type of thing this is, provided it exists in the group mapping db, we should not bother winbindd here. Andrew Bartlett (This used to be commit d626b5c6d401e72296cf570e50f324c145fd70e0)
Diffstat (limited to 'source3/stf/osver.py')
0 files changed, 0 insertions, 0 deletions