[389-users] Re: status of the LDAP REST API
On 04/12/2018 10:38 AM, Stephen Osella wrote: > What is the status of the LDAP REST API? As described at: > > http://directory.fedoraproject.org/docs/389ds/design/ldap-rest-api.html This project is unfortunately on hold (permanently?). We are writing the new UI as a Cockpit plugin (which does not support a REST interface/routing). > ___ > 389-users mailing list -- 389-users@lists.fedoraproject.org > To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
[389-users] status of the LDAP REST API
What is the status of the LDAP REST API? As described at: http://directory.fedoraproject.org/docs/389ds/design/ldap-rest-api.html ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
[389-users] sd_notify called before 389-ds really ready?
I have a service on my 389-ds host that is configured in systemd to depend on 389-ds and start after dirsrv.target. However, unless I add a sleep (ExecStartPre systemd stanza) to the startup of that other service it fails to start as 389 is not fully ready. I can see that systemd is respecting the dependencies, but the client starts before 389 is able to accept its connection. 389-ds appears to use the notify systemd service type. Is it possible that sd_notify is being called before the services are truly ready to accept client connections? ___ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org