operational attributes in back-config?

[Pierangelo Masarati <ando@sys-net.it>]

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?

p.


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