On 30 Aug 2019, at 21:10, Nicolas Kovacs <info(a)microlinux.fr>
Over the last couple of weeks, I've experimented quite a lot with 389
Directory Server. I've had good help on this list, so I wanted to thank
I've started to write a series of blog articles about 389 DS, and I've
added two honorable mentions for Marc Muehlfeld and William Brown, who
have provided precious information.
I have been super happy to help, as I'm sure Marc is too!
My french is not so good but as an obvious review point, pam_limits and the ulimit changes
you have made are not needed on RHEL 7 - systemd bypasses them as service start, and we
ship a pre-configured unit file that has all the correct limits.
Additionally, we also ship a sysctl drop in that automatically alters your system's
sysctl to be correct for ldap services too.
We have taken a "correct by default" stance for some years to make installs as
simple as possible :)
The dirsrv.target now has no effect either because the dirsrv@service should be linked
against the multi-user.target, so you shouldn't need to manage that. Simply
start/stop/enable/disable the "dirsrv(a)instance.service" unit.
Really happy to see you blogging about 389, and I hope to see more great content from you
in the future!
Cheers from the sunny South of France,
Microlinux - Solutions informatiques durables
7, place de l'église - 30730 Montpezat
Site : https://www.microlinux.fr
Mail : info(a)microlinux.fr
Tél. : 04 66 63 10 32
Mob. : 06 51 80 12 12
389-users mailing list -- 389-users(a)lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave(a)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
Senior Software Engineer, 389 Directory Server