similar to: Samba 3.0.14 and 3.0.15pre1 contain a bad assert line

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== If two heads are better than one, why do my shoulders hurt so much? -- Michael Samuel Finn ============================================================== Release Announcements ===================== The Samba Team

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== If two heads are better than one, why do my shoulders hurt so much? -- Michael Samuel Finn ============================================================== Release Announcements ===================== The Samba Team

I have a Samba 3.0.15pre1 box running winbind to a Windows 2003 AD Domain, see the smb.conf file below. If I run 'wbinfo -u' it returns all the expected user and computer accounts, in lower case. I just compiled and installed 3.0.20 and now 'wbinfo -u' is returning mixed-case results. I am guessing that the mixed-case results are exactly what the AD servers are returning to

Hi, I'm interested in the update of the samba version in one of our servers, but I'm confused: http://www.samba.org says the last stable version of samba is 3.0.14, but the link is not working, and in various ftp mirrors, in their "stable" subdirectory, I see the 3.0.9 versi?n as the last versi?n. What's happening? Can you help me? Thanks --

Samba 3.0.11, 3.0.14a, 3.0.15pre1 on Red Hat RHAS3 Samba server is an NT4 PDC (no ADS) passdb backend = ldapsam I could try it out for myself, since I've a test machine besides my regular site. But I'd really rather have a definitive answer. I have POSIX ACLs working fine. In smb.conf I set "nt acl support = yes" (default anyway). Let's presume that I go and put all