[389-users] Re: 389-ds opensuse container questions

> On 6 Jun 2022, at 12:12, tdarby@email.arizona.edu wrote:
>
> Thanks! I've succeeded in getting all my configs scripted with Python, except for setting the nsslapd-db-locks attribute:
>
> standalone.conig,set (fail)
> dse_ldif.replace (fail)
> dsconf works!
>
> What's the magic here? Is there a Pythonic way to do this?

The magic is likely that dse.ldif, if changed while the server is running is will automatically revert your changes from "in memory". This is because 389-ds can "live" update it's config.

So dsconf is using the ldap-facing live update mechanism, which means ns-slapd writes the changes down to dse.ldif. That's probably what you are encountering.

>
> Also, I'm surpsised at how much I had to resort to Python LDAP to get things done. I kinda thought that lib389 would do most of it?

What did you find was missing?


--
Sincerely,

William Brown

Senior Software Engineer,
Identity and Access Management
SUSE Labs, Australia
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure