[Date Prev][Date Next] [Chronological] [Thread] [Top]

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

To: openldap-devel@openldap.org
Subject: Re: Slapd startup behavior when unable to bind to an interface
From: ml+openldap@esmtp.org
Date: Sat, 9 Jan 2016 17:36:15 -0800
Content-disposition: inline
In-reply-to: <3C4675616E42CA0200E4AE9A@[192.168.1.9]>
Mail-followup-to: openldap-devel@openldap.org
References: <3C4675616E42CA0200E4AE9A@[192.168.1.9]>
User-agent: Mutt/1.5.24+24 (4de4b3635140) (2015-08-30)

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.

References:
- Slapd startup behavior when unable to bind to an interface
  - From: Quanah Gibson-Mount <quanah@zimbra.com>

Prev by Date: Slapd startup behavior when unable to bind to an interface
Next by Date: Re: Slapd startup behavior when unable to bind to an interface
Index(es):
- Chronological
- Thread