On Mon, 2017-06-19 at 16:46 +0200, Karsten Heymann wrote:
> Hi Howard,
>
> perfect, thank you. I missed that one, I searched the documentation
> for "port", "listen" and "limit" but didn't think about the socket
> term. I guess for urls it's sockurl, sockname seems to be ment for the
> socket
I know. But that is not my problem.
On Mon, Jun 19, 2017 at 2:31 PM, Klaus Malorny
wrote:
> On 6/19/17 10:31 AM, Muhammed Muneer wrote:
>
>> Sorry for the late reply, I was on vacation.
>>
>> Klaus wrote:
>> "I am still unsure what you are trying to achieve. If you are
Hi Howard,
perfect, thank you. I missed that one, I searched the documentation
for "port", "listen" and "limit" but didn't think about the socket
term. I guess for urls it's sockurl, sockname seems to be ment for the
socket (file) name.
Best regards
Karsten
2017-06-19 15:48 GMT+02:00 Howard Chu
On Thu, Jun 15, 2017 at 01:35:45PM +0200, Jelle de Jong wrote:
> Hello everybody,
>
> # my /etc/ldap/slapd.conf
> http://paste.debian.net/plainh/076816e3
Do slapd's logs have any clues? Service restarting, resource issues?
--
Brian Reichert
BSD
Karsten Heymann wrote:
Hi,
short question: If I configure slapd to listen to several ports and
have several databases configured, is there a way to limit which
database is visible on which port? I want to use a single slapd
instance to serve multiple databases (slapd-meta instances to be
exact)
opensou...@gmx-topmail.de wrote:
Are you running multiple Docker instances on the same database? AFAIK that
won't work because of Docker's munging with POSIX namespaces.
No, it is a Single Docker instance. Actually, I saw the same thing happening on
a Ubuntu box, so it should not be related
Abdelkader Chelouah wrote:
Elliptic Curve support for OpenSSL was added in master branch 4 years ago
(ITS#7595). Is there any plan to backport EC support for OpenSSL in 2.4 branch ?
OpenLDAP 2.4 is feature-frozen. All new features are 2.5 only.
--
-- Howard Chu
CTO, Symas Corp.
Hi,
short question: If I configure slapd to listen to several ports and
have several databases configured, is there a way to limit which
database is visible on which port? I want to use a single slapd
instance to serve multiple databases (slapd-meta instances to be
exact) and for each database
On Fri, Jun 16, 2017 at 03:26:20PM +, Daniel Le wrote:
>Hi,
>
>
>I'm seeing some critical error which causes the application program to
>exit/terminate when ldap_start_tls_s(LDAP-handle, NULL, NULL) is
>called. Tracing the code execution, ldap_start_tls_s =>
>
> Are you running multiple Docker instances on the same database? AFAIK that
> won't work because of Docker's munging with POSIX namespaces.
No, it is a Single Docker instance. Actually, I saw the same thing happening on
a Ubuntu box, so it should not be related to Docker.
I restructured the CI
Elliptic Curve support for OpenSSL was added in master branch 4 years
ago (ITS#7595). Is there any plan to backport EC support for OpenSSL in
2.4 branch ?
On 6/19/17 10:31 AM, Muhammed Muneer wrote:
Sorry for the late reply, I was on vacation.
Klaus wrote:
"I am still unsure what you are trying to achieve. If you are in a read
transaction and discover that your database does not exist, what can you do
anyway? You cannot create the database at
Sorry for the late reply, I was on vacation.
Klaus wrote:
"I am still unsure what you are trying to achieve. If you are in a read
transaction and discover that your database does not exist, what can you do
anyway? You cannot create the database at this point, since it is a write
operation."
When
13 matches
Mail list logo