On Fri, Mar 11, 2022 at 10:47:53AM -0800, Quanah Gibson-Mount wrote: > --On Friday, March 11, 2022 12:25 PM +0100 Ondřej Kuzník > <[email protected]> wrote: >> If you configure syncprov-sessionlog-source, adding syncprov-sessionlog >> to the mix will do nothing except eat memory, as the manpage and the >> logs will happily point out. If you're using plain syncrepl, you have a >> choice to store and use accesslog or stay the traditional sessionlog, >> both work fine but sure, there are tradeoffs. Since AFAIK anything >> persisted needs to be an LDAP entry, the silver bullet just isn't >> available. > > The issue is that to use the disk based sessionlog, you also have to set up > a full delta-based accesslog. If one could simply store only the necessary > data for the sessionlog in the accesslog DB and skip the other ops then it > would be a fine solution.
As previously mentioned, it has to be an actual LDAP database, so the only way we could improve on this situation is by not storing reqMod: values. Everything else is either needed to make it a valid LDAP entry or necessary to support sessionlog. Regards, -- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP
