Hi all,
Does anybody have an idea what the problem might be?
I have found the reason for the problem: Samba 3.0.23 and
3.0.23a do not parse the passdb backend entry in the smb.conf
correctly anymore (tested on Debian Sarge and FreeBSD 6.1).
According to the smb.conf man page, it is allowed to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Uwe Laverenz wrote:
According to the smb.conf man page, it is allowed to
put the ldap URIs in double qoutes:
passdb backend = ldapsam:ldap://ldap-1.example.com \
ldap://ldap-2.example.com;
This does not work for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This time with the correct file attached.
Gerald (Jerry) Carter wrote:
Uwe Laverenz wrote:
According to the smb.conf man page, it is allowed to
put the ldap URIs in double qoutes:
passdb backend = ldapsam:ldap://ldap-1.example.com \
On Thu, 2006-07-27 at 07:15 -0500, Gerald (Jerry) Carter wrote:
Uwe Laverenz wrote:
According to the smb.conf man page, it is allowed to
put the ldap URIs in double qoutes:
passdb backend = ldapsam:ldap://ldap-1.example.com \
ldap://ldap-2.example.com;
Hi Jerry,
On Thu, Jul 27, 2006 at 07:18:48AM -0500, Gerald (Jerry) Carter wrote:
H...that should work. It certainly wasn't an
intentional change. This patch should correct it.
I tested it on my FreeBSD workstation and it works perfectly. :)
Thank you!
Uwe
--
To unsubscribe from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Uwe Laverenz wrote:
Hi Jerry,
On Thu, Jul 27, 2006 at 07:18:48AM -0500, Gerald (Jerry) Carter wrote:
H...that should work. It certainly wasn't an
intentional change. This patch should correct it.
I tested it on my FreeBSD workstation
