Hi,
I used 389 Directory Server in the past but it has been a long time...
Problem 1:
---
When I start 389-console on top of an ssh session with X, I can't use
the input boxes...
(solved by a local installation of 389-ds but...)
Problem 2:
---
I see for an easy setup
These 2 links should help, 389 has its own cert management, so it is a bit
different at first, you can probably use pk12util and certutil to do most of
the cert handling.
http://directory.fedoraproject.org/wiki/FAQ#Can_389_use_OpenSSL_or_GnuTLS.3F
http://directory.fedoraproject.org/wiki/Howto:SSL
Hi,
I encountered the following logs in the errors:
[06/Oct/2011:10:11:57 +] NSMMReplicationPlugin - changelog program -
agmt=cn=srvAtosrvB (srvB:389): CSN 4e8d804a000c not found, we aren't
as up to date, or we purged
[06/Oct/2011:10:11:57 +] NSMMReplicationPlugin -
On 10/11/2011 01:22 PM, Reinhard Nappert wrote:
Hi,
I encountered the following logs in the errors:
[06/Oct/2011:10:11:57 +] NSMMReplicationPlugin - changelog program -
agmt=cn=srvAtosrvB (srvB:389): CSN 4e8d804a000c not found, we aren't
as up to date, or we purged
How do I do this manually on server A?
The other question is, what kind of impact does it have when I re-iitialize
server B? To be more precise, my replication environment is more complex than
just server A and server B. In fact, I have a setup like the following:
srv C -- srv A -- srv B --
