we are using 389 in production environment since 2006 or 2007. It is a
central authentication/authorization mechanism for ~20000 accounts,
~500 (occasional search from 5000) workstations, ~20-30 web
We have 3 multi-masters in replication. Everything is very stable so far.
You may have problems if you check-out and compile the code or install
the latest development (alpha or non-stable, early rc) versions. I
would recommend 18.104.22.168 as the latest stable version.
The only support for 389 is the web site wiki, this list and bugzilla,
the developers in general are available and very reactive, it happened
several times that a patch for a bug that i filed was available in
less than 24 hours...
However you should acquire yourself some skills since you (the server
admin) are the last resort in case of a problem, not RedHat or
If you want a commercial support you should go for RedHat Directory
Server. RedHat also has the training for RHDS Administration...
2011/10/21 Alex Pershyn <Alex.Pershyn(a)enabil.com>:
Can anybody tell me about using 389 in production environment? Is it stable?
Were there many issues with it? Is there any support in case of production
Application architect, Enabil Solutions Ltd
389 users mailing list