[Samba] LDAP items that might help for How-to

[Tony Earnshaw]

John H Terpstra:

[...]

> Gavin is correct here. Thanks for the input but on this occassion it
> seems I need to add more reference to scanning the logs. I'll think about
> the best way to tackle that.

Yes, gavin is correct. However, it's not just a question of scanning the
logs, but also interpreting them correctly.

I run Red Hat RHAS. Mostly /etc/rc.d/init.d/ldap (my own implementation)
will let you see what goes on at daemon startup. But if it doesn't (which
can happen quite a lot), it is often useful to start up the daemon by hand
at the CLI, using the command line in the ldap script. The debug level can
then be configured in the CLI command.

Like in my RH startup script I have:

daemon ${slapd} -u ldap -h "ldap://tru.leerlingen/ ldaps://tru.leerlingen/
ldapi://%2Fusr%2Flocal%2Fvar%2Fslapd%2Fldapi/????x-mod=0777" $OPTIONS
$SLAPD_OPTIONS

This presupposes multiple xterm windows open, ALT from the one to the other..

"service ldap stop"

At the CLI I substitute.

'slapd -u ldap -d 256 -h "ldap://whatever.host/ ldaps://whatever.host/
ldapi://%2Fusr%2Flocal%2Fvar%2Fslapd%2Fldapi/????x-mod=0777"'

**** Change the "-d" bit to whatever suits.

**** Leave out the "ldapi" bit, if you don't understand or use it.

**** Leave out the "ldaps" bit, if you don't understand or use it.

If there are any slapd.conf faults or whatever, the CLI startup line will
detail them.

--Tonni

Baaie dankie aan/Many thanks to Exim's Philip Hazel who taught me to think
this way, before I left Exim for Postfix.

--
mail: tonye at billy.demon.nl
http://www.billy.demon.nl