[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
OpenLDAP amd64/i386 weirdness
- To: freebsd-questions_(_at_)_freebsd_(_dot_)_org
- Subject: OpenLDAP amd64/i386 weirdness
- From: "O. Hartmann" <ohartman_(_at_)_zedat_(_dot_)_fu-berlin_(_dot_)_de>
- Date: Tue, 26 Aug 2008 08:25:19 +0000
- Organization: Freie Universität Berlin
I made some strange experiences in running OpenLDAP 2.4.11 on both i386
and amd64 architectures of the most recent FreeBSD 7.0-STABLE.
I already setup and run three servers (fourth is coming soon). Two of
them are based on FreeBSD amd64, one is based on i386. The do have
almost the same configuration, the same portrevision of both nss_ldap
and pam_ldap I need to use (nss_ldap-1.257, pam_ldap-1.8.4), and, of
course, the same OpenLDAP port
(openldap-sasl-client-2.4.11,openldap-sasl-server-2.4.11) an the same
SASL2 libraries taken from port (cyrus-sasl-ldapdb-2.1.22). So, this is
the base on ALL boxes! Also the changes in /etc/pam.d/system,
/etc/pam.d/sshd, /etc/pam.d/other and /etc/pam.d/passwd are exactly the
So, now the weird thing.
On all amd64-boxes I can config /etc/nsswitch.conf this way and it works:
The manpages do not reveal anything about 'ldap' is allowed (FreeBSD is
in this case far behind anything else out the server market, a shame), I
tried it and had success on all of my amd64-boxes. But using the same on
the third i386-server fails. And now I'm asking myself what I've done
magic or wrong or have overseen (a small piece in the chain of
configurations) or is there indeed a difference between amd64 and i386
in handling this?
Thanks in advance,
P.S. Please respond to my email also, I'm not subscriber of the
'questions' list. Thank you.
freebsd-questions_(_at_)_freebsd_(_dot_)_org mailing list
To unsubscribe, send any mail to "freebsd-questions-unsubscribe_(_at_)_freebsd_(_dot_)_org"
Visit your host, monkey.org