Re: Slapd startup behavior when unable to bind to an interface

On Sat, Jan 09, 2016, Quanah Gibson-Mount wrote:

Currently, slapd will start up even if it can't bind to an interface, if more than one potential interface is given where the bind is successful.

FWIW: sendmail had the inverse problem and it was resolved by marking an "interface" as optional: DaemonPortOptions: Modifier Options (flags) for the daemon O optional; if opening the socket fails ignore it This was done so a (generic) cf file could have both IPv4 and IPv6 DaemonPortOptions (sockets) without failing to start when IPv6 isn't available.