Hi Kees,
That should be:
dsconf instance backend config set --deadlock-policy policy
That should be:
dsconf instance backend config set --deadlock-policy policy
Regards
Pierre
On Mon, Aug 30, 2021 at 8:50 PM Kees Bakker <keesb@ghs.com> wrote:
On 30-08-2021 14:16, Mark Reynolds wrote:
> On 8/30/21 4:20 AM, Kees Bakker wrote:
>> Hi,
>>
>> In one of the GitHub issues [1] it was mentioned that
>> > People "should" be using the python CLI & UI to make these config
>> changes
>>
>> What CLI and/or UI is this?
>
> Starting in 389-ds-base-1.4.x we offer a web UI Cockpit plugin:
> cockpit-389-ds. We also have a extensive python CLI toolset: dsconf,
> dsctl, dsidm, and dscreate. These are all documented in the Admin guide.
>
> https://access.redhat.com/documentation/en-us/red_hat_directory_server/11/html/administration_guide/index
>
> For db deadlock policy you would use dsconf like this:
>
> dsconf slapd-YOUR_INSTANCE backend config set --deadlock-policy 6
>
> HTH,
>
> Mark
Ah. Thanks a lot.
>
>>
>> For example, what is the preferred way to change
>> nsslapd-db-deadlock-policy?
>>
>> [1] https://github.com/389ds/389-ds-base/issues/4869
>
> --
> Directory Server Development Team
>
_______________________________________________
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
--
389 Directory Server Development Team
389 Directory Server Development Team
No comments:
Post a Comment