This formatting looks weird?

How big is maxpathlen?

Thanks @firstyear for the review. formatting is indeed weird, side effect of my editor. I will fix this. MAXPATHLEN (via params.h) is a define for PATH_MAX /usr/include/linux/limits.h, it is 4096 bytes.

LGTM

Great, seems okay to me then. Ack.

This function should be a part of a fixture. It won't work as a finalizer for the test function.

I'd rather use existing lib389 modules for that. You can get it like this:

 inst = DirSrv(verbose=True, external_log=log)
 dse_ldif = DSEldif(inst,
                    serverid="test_longname_deadbeef_deadbeef_deadbeef_deadbeef_deadbeef")
 socket_path = dse_ldif.get("cn=config", "nsslapd-ldapifilepath")
 inst.local_simple_allocate(
    serverid="test_longname_deadbeef_deadbeef_deadbeef_deadbeef_deadbeef",
    ldapuri=f"ldapi://{socket_path[0].replace('/', '%2f')}",
   password="someLongPassword_123"
)
inst.ldapi_enabled = 'on'
inst.ldapi_socket = socket_path
inst.ldapi_autobind = 'off'
inst.open()

Feel free to change hardcoded values to variables.

A search to RootDSE can be done through existing DSLdapObject:

root_dse = RootDSE(dscreate_ldapi_instance)
print(root_dse.get_supported_ctrls())

Please, note, that you need this fix for my proposal to work:
https://pagure.io/389-ds-base/pull-request/50587

Please, note, that you need this fix for my proposal to work:
https://pagure.io/389-ds-base/pull-request/50587

The PR above was merged. I need to do upstream builds, but we need this fix merged first. Is this ready now?

The rebase is from a change proposed by @spichugi . It works like a charm but still have a minor issue that the fixture finalizer is not systematically called (for example when the server crash).

The purpose of this last patch is to allow fixture finalizer to be called during a DS crash during fixture run.

Probably, makes sense to put test_longname_deadbeef_deadbeef_deadbeef_deadbeef_deadbeef into some variable and then reuse it

Can be log.info instead of the print. (I sent it like this only for a faster example of what I had in mind)

Besides these two minor issues, you have my ack!
Thanks!

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This pull request has been cloned to Github as issue and is available here:
- https://github.com/389ds/389-ds-base/issues/3638

If you want to continue to work on the PR, please navigate to the github issue,
download the patch from the attachments and file a new pull request.

Thank you for understanding. We apologize for all inconvenience.