i configured nsslapd-enable-nunc-stans in dse.ldif and started dirsrv. I verified that the setting is set with:
$ ldapsearch -D 'cn=Directory Manager' -y p -h localhost -b 'cn=config' | grep nsslapd-enable-nunc-stans nsslapd-enable-nunc-stans: on
I would expect:
strace -fF -s 1024 -p $(pidof ns-slapd)
To show epoll syscalls but instead i am still seeing select syscalls.
ldd /usr/lib64/dirsrv/libnunc-stans.so.0 linux-vdso.so.1 (0x00007fffa99fa000) libevent-2.1.so.6 => /usr/lib64/libevent-2.1.so.6 (0x00007efc603f1000) libsds.so.0 => /usr/lib64/dirsrv/libsds.so.0 (0x00007efc601e4000) [snip] ldd /usr/lib/389-ds/sbin/ns-slapd linux-vdso.so.1 (0x00007ffebb1fc000) libnunc-stans.so.0 => /usr/lib64/dirsrv/libnunc-stans.so.0 (0x00007f32a9448000) [snip]
openSUSE Tumbleweed
libsvrcore0-4.1.3-24.4.x86_64 389-ds-1.3.6.4-34.6.x86_64
build log: https://build.opensuse.org/public/build/home:darix:playground/openSUSE_Tumbleweed/x86_64/389-ds/_log
source package:
small update: when putting queries onto the 389-ds it starts using epoll. what is the select loop for then?
From IRC conversation:
richm: what is the select thread used for? either waiting for output ready on a single fd, or instead of sleep() richm: aha
Closing ticket.
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 issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2310
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: invalid)