during samba4 initial startup - the failure to bind to the NEEDED ldap backend - is ignored. Should be a fatal error

[Günter Kukkukk]

Here the samba3 related openldap daemon was already running by mistake.

From IRC the failing samba4 debug 3 outcome:

02/28/12  4:47:57 <kukks> when _carefully_ looking at the s4 debug 3 outcome - i should have noticed:
02/28/12  4:47:58 <kukks> Failed to listen on 0.0.0.0:389 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED
02/28/12  4:47:58 <kukks> ldapsrv failed to bind to 0.0.0.0:389 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED
02/28/12  4:47:58 <kukks> task_server_terminate: [Failed to startup ldap server task]
02/28/12  4:47:58 <kukks> single_terminate: reason[Failed to startup ldap server task]

Samba4 should _terminate_ (!) here - no LDAP server bind available!

Atm - samba4 init just goes on... failures lateron.

Cheers, Günter