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

Re: operational attributes in back-config?

Howard Chu wrote:

Pierangelo Masarati wrote:

I note that structuralObjectClass gets into permanent storage of back-config; however, other relevant operational attributes don't. Is it intended or what? I'm mainly thinking about createTimestamp, modifytimestamp and so; creatorsName and modifiersName may not be an issue, since only the rootdn can write back-config, and the rootdn is hardcoded to cn=config. Other relevant attributes may be entryUUID, if of any use. Could the timestamps in back-ldif be inherited from the filesystem?

The rootdn is initialized to cn=config, but it can still be explicitly set to anything else.

OK, I missed this; I seem to recall that at some point this was not (yet) possible.

The lack of these other operational attributes is an oversight. They didn't seem useful at first, but are certainly necessary for things like syncrepl to work.

In case, I might give it a look. I'm mostly interested in createTimestamp, modifyTimestamp.


SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497