[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Config questions for back-ldap, back-meta, and back-asyncmeta
- To: Howard Chu <hyc@symas.com>, Quanah Gibson-Mount <quanah@symas.com>, openldap-devel@openldap.org
- Subject: Re: Config questions for back-ldap, back-meta, and back-asyncmeta
- From: Michael Ströder <michael@stroeder.com>
- Date: Fri, 15 Jun 2018 00:04:41 +0200
- Autocrypt: addr=michael@stroeder.com; prefer-encrypt=mutual; keydata= xsBNBFbdnRoBCADj0vYA4aRwKJ6AE4mf8oElLgMT/1eLNKpJ2FYBWcwj9d8dTk5/p9b8DRxy S/qQIUUZqt9xRFZwUCm0vFeQMRDeN9xzAKoRzrJifoDOacOjG1lhZTKYvVZGgUT89Ao3QeHh Q7gPzcAKNoueoR2y3FXStOYuRrbk5PlSjVAITjsotgc7PWE9mmVYpeu8a+byK/DBHKUyolOA 1UXYvDa7MbPhMtdNm8qnwtKs1Vsyk1VkErM+5cIe+zTT6WYQcmZMRjCtWGiFTzk9W6Mdlskk WRTKhKNgokTsgcy1ecaCBUZWxv/SyXgD81+rwRi9b8Px+1reg43ayxi8sV7jrI1feybbABEB AAHNJ01pY2hhZWwgU3Ryw7ZkZXIgPG1pY2hhZWxAc3Ryb2VkZXIuY29tPsLAdwQTAQgAIQUC Vt2dGgIbAwULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRAH3HrjaovJOFpTCACjO773gcmJ KvzjiNpUFl/gANyaJgIq4VbMQ7VthRb1F9X6YbdJ6Z99ntyESjGFCpjofcSomr2vJDpv6ht+ lY33yo20YwsMpqe2OeId0jPybG+FtabKjgBNoAk7iqnBGUvE4t0dz0n1LQVCQR2jxyTKmcNq OYpsRZ3H+6kWwJMuVgsNZglINVZ8JgV5QuLYN5jhYz+pOuFnU11bV6nWREvzZXzebe7g7Zus 6AsWjtJ0lDvgBNzLlF3/eFrVch6Bejs0SvuFseIdZQk+4YU6Rb8xul/jDFXIfo7eTmijO3dV T5AmC1cUi8czncwpgAJnEH8vYv23RoN/aw2gSMCS2huIzsBNBFbdnRoBCAC7L1cTVBVZZuM/ yxSUM5CsgGBlTD1Cr7C2ngZFsHSYXVLq6NUB8GZA2iLK96CrwnFw4/Jjz4llOjc50iVRMQKL RyFWOJAMrpPq2ew5T+Uoo524D//dwVbqkFVVuvM8NPiKIDyPGCjP+acM1D8hXwhOXgQ8Iz8Q 3/GRSYjitn9JrkF0ia2nhariznBKVu0LDffxF/hOCx45+QRR2/rYYlshfZMB7nEJX9P+hVfM CSzltz9Z8CldeUbiJvnyrISReR2XBw9oh8JkIUP0BtpIaify9A7EfzOk+W9BUnWe+YwdSUsB fJxOhSv+umyW5GMqZGFu+4oYnkzbe+1LUs1JarCtABEBAAHCwF8EGAEIAAkFAlbdnRoCGwwA CgkQB9x642qLyTjEUgf+JX6Atatl/QKe37yCj1OZYNPd3B0rPLJRF5mEmrADRXLZC9+uFeDS Wxxln040gnR6rjBHrRcvVmlTDiZY26iuL16+V+0/aZ9uyXNQSzk2cwDSiI/8gvr72Y+FN5fh cGXpeNHxHilYc9onzDhxyE76cwzqTKm4q2ULIH2u9IHQ5O86Fv6nHPYhe2fy1bhQapNwi/Xl 3G3i2WNH/w7m+1zWU1IddZOjmXzoxLT1BATwXGa0Tt5RjVb2mM1Wg3Zj6kqFkF2vvKcvrwj0 q0Ap5uyfN5m0uWzQMCMoaV9HQf7f5MkS1lnwBqDgnojjVAieX5uk7olUiRuPKHMfhvXulYP8 AA==
- In-reply-to: <00ba9936-2d1a-7c3c-ede0-516da8148be4@symas.com>
- Openpgp: preference=signencrypt
- References: <AAFB8B037CF263B1972878C2@[192.168.1.10]> <1fbe2282-b695-6266-85a9-28a9ff667806@symas.com> <88ebfeb3-9c2e-881b-96f5-7ef42e1d7e33@stroeder.com> <00ba9936-2d1a-7c3c-ede0-516da8148be4@symas.com>
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
On 06/14/2018 11:58 PM, Howard Chu wrote:
> Michael Ströder wrote:
>> On 06/14/2018 10:44 PM, Howard Chu wrote:
>>> Quanah Gibson-Mount wrote:
>>>> idle-timeout -> The man page says takes an integer, but is defined as
>>>> a string. However, I think the man page for this parameter is
>>>> incorrect, and in fact it takes a possible string as defined in the
>>>> back-meta/async manual pages for this same parameter. (I.e, it can
>>>> have a format of something like 1d15h5s)
>>>
>>> I don't see this. The man page says "<time>". It looks correct to me.
>>
>> Wouldn't it be better to consequently convert time strings such as
>> 1d15h5s to integer seconds during migration of static config to dynamic
>> config? IMO for LDAP-on-the-wire those values should always be integer
>> representing seconds (or milli-seconds if needed).
>>
>> I mean back-config content is meant to be machine-processable and
>> cleaner syntax would reduce unneeded complexity.
>
> The complexity is already there, and obviously somebody thought it was
> desirable for these things to be human-readable. We're doing them no
> favors by converting to straight integers.
It's not only about the complexity in OpenLDAP software itself. All
3rd-party components which want to make use of back-config for automated
configuration have to deal with it. And that's not going to happen.
Ciao, Michael.
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature