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

Re: LMDB and FD_CLOEXEC

To: Martin Lucina <martin@lucina.net>
Subject: Re: LMDB and FD_CLOEXEC
From: Hallvard Breien Furuseth <h.b.furuseth@usit.uio.no>
Date: Tue, 11 Mar 2014 16:32:47 +0000
Accept-language: en-GB, en-US
Cc: "openldap-technical@openldap.org" <openldap-technical@openldap.org>
Content-id: <FEED01BABAB3904D8C1EFD4C8F89FFEE@mail.uio.no>
Content-language: en-US
In-reply-to: <20140311090348.GB31331@nodbug.moloch.sk>
References: <20140310211409.GB22062@nodbug.moloch.sk> <1394496062.10288.2.camel@mysil.uio.no> <20140311090348.GB31331@nodbug.moloch.sk>
Thread-index: AQHPPKpC70yu+gTp7kKduZWpWjB0apra7+IAgACXpgCAAHdQAA==
Thread-topic: LMDB and FD_CLOEXEC

On Tue, 2014-03-11 at 10:03 +0100, Martin Lucina wrote:
> h.b.furuseth@usit.uio.no said:
>> It sets it to get rid of the file lock on the lockfile,
>> and does not bother with the others.
> 
> In that case can I suggest adding FD_CLOEXEC to the other descriptors? I'm
> using MDB in a program that spawns other processes and I'd prefer not to
> leak the fds to them.

Sounds like a fine opportunity to factor out some #ifdef _WIN32 stuff:-)

-- 
Hallvard

References:
- LMDB and FD_CLOEXEC
  - From: Martin Lucina <martin@lucina.net>
- Re: LMDB and FD_CLOEXEC
  - From: Hallvard Breien Furuseth <h.b.furuseth@usit.uio.no>
- Re: LMDB and FD_CLOEXEC
  - From: Martin Lucina <martin@lucina.net>

Prev by Date: RE: Antw: open(ldap|ssh) interaction
Next by Date: Kerberos issue running OpenLDAP on Mac OS X Mavericks
Index(es):
- Chronological
- Thread