Re: [Samba] Proposed patches for inclusion in Samba 3.0.25a

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alex Crow wrote: > I cleared out *all* my samba files apart from smb.conf > and it now seems to be working correctly. Excellent! Thanks for the update. cheers, jerry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Usi

Re: [Samba] Proposed patches for inclusion in Samba 3.0.25a

On Tue, 2007-05-22 at 14:06 -0500, Gerald (Jerry) Carter wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Alex Crow wrote: > > Jerry, > > > > I *think* it coinided with using the user/group selection > > dialog in the "Security" tab for a file share. > > > > As for the segafault, I'

Re: [Samba] Proposed patches for inclusion in Samba 3.0.25a

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alex Crow wrote: > Jerry, > > I *think* it coinided with using the user/group selection > dialog in the "Security" tab for a file share. > > As for the segafault, I'm going to try make a fresh OS > install on the machine tomorrow and start again as

Re: [Samba] Proposed patches for inclusion in Samba 3.0.25a

Jerry, I *think* it coinided with using the user/group selection dialog in the "Security" tab for a file share. As for the segafault, I'm going to try make a fresh OS install on the machine tomorrow and start again as I think I might have some residues somewhere... As I said, RC3 was working fin

Re: [Samba] Proposed patches for inclusion in Samba 3.0.25a

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alex Crow wrote: > Gerry, > > I'm afraid that patch has almost rendered the server uncontactable. I am > now getting constant errors in smbd connecting to my LDAP server: > > May 22 14:36:52 print smbd: nss_ldap: failed to bind to LDAP server > ldap:

Re: [Samba] Proposed patches for inclusion in Samba 3.0.25a

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alex, >> It seem like your ldap server is down. >> > > If it was, my whole office would be phoning me now - > > we have: > > 3 slave ldap servers > 2 mail servers > 1 BDC > 6 member servers > 1 telephone directory web page > 250 users using LDAP fo

Re: [Samba] Proposed patches for inclusion in Samba 3.0.25a

> It seem like your ldap server is down. > If it was, my whole office would be phoning me now - we have: 3 slave ldap servers 2 mail servers 1 BDC 6 member servers 1 telephone directory web page 250 users using LDAP for their address book. All are working correctly so it's *not* this. This ha

Re: [Samba] Proposed patches for inclusion in Samba 3.0.25a

On Tue, 2007-05-22 at 14:44 +0100, Alex Crow wrote: > Gerry, > > I'm afraid that patch has almost rendered the server uncontactable. I am > now getting constant errors in smbd connecting to my LDAP server: > > May 22 14:36:52 print smbd: nss_ldap: failed to bind to LDAP server > ldap://pdc.ifa.ne

Re: [Samba] Proposed patches for inclusion in Samba 3.0.25a

Gerry, I'm afraid that patch has almost rendered the server uncontactable. I am now getting constant errors in smbd connecting to my LDAP server: May 22 14:36:52 print smbd: nss_ldap: failed to bind to LDAP server ldap://pdc.ifa.net: Can't contact LDAP server May 22 14:36:52 print smbd: nss_ldap:

Re: [Samba] Proposed patches for inclusion in Samba 3.0.25a

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gerald (Jerry) Carter wrote: > Folks, > > I've cobbled together the svn commits for SAMBA_3_0_25 that > address a few very visible bugs in 3.0.25: > > * The object picker error for "security = domain" > * Supplementary group membership bug with "forc

[Samba] Proposed patches for inclusion in Samba 3.0.25a

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Folks, I've cobbled together the svn commits for SAMBA_3_0_25 that address a few very visible bugs in 3.0.25: * The object picker error for "security = domain" * Supplementary group membership bug with "force group" * Premature password expiration on