You mentioned 2 servers ldap1 and ldap2. Are they both masters? You put
local consumer to ldap2. Does that mean ldap2 is a read only replica?
We have two data centers and each data center has an ldap1 and ldap2. All
4 are masters, but we only ever send updates to DCA-ldap1. That then
Hi,
Please remove me from this list.
Thank you,
David
On 23 Apr 2014, at 15:14, Elizabeth Jones bajo...@panix.com wrote:
You mentioned 2 servers ldap1 and ldap2. Are they both masters? You put
local consumer to ldap2. Does that mean ldap2 is a read only replica?
We have two data
inspect the mail headers - you can remove yourself as is the case with most
mailing lists these days.
/mrg
On Apr 23, 2014, at 10:38 AM, David Hall da...@rocketcommunications.co.uk
wrote:
Hi,
Please remove me from this list.
Thank you,
David
On 23 Apr 2014, at 15:14, Elizabeth
Elizabeth Jones wrote:
I will give this a shot. When we tried to initialize these last week the
initialization emptied out the receiving ldap and I believe that was a bug
that is fixed in 1.3. I recovered by using a backup but I don't want to
try initializing again until we can upgrade to 1.3.
I'd like to try out the web interface, and I'm trying to follow along with
some tips I've found online. I have dsgw installed on my server
(389-dsgw-1.1.11-1.el6.x86_64). I ran the setup-ds-dsgw script and
restarted the admin server, but going to http:my_ip:9830 just times out.
If I copy
http://directory.fedoraproject.org/wiki/Howto:Default_Console_Object_Object
class
==
Regards,
Matthew Schmitt
mschm...@sugarsync.com
On 4/23/14, 10:42 AM, Ssureshot ssures...@gmail.com wrote:
I've added the inetUser object class to the nsdefaultobjectclass the the
OK, I may have spoken a bit too soon. The reason I can't browse to it is
because of our firewall. We block port 9830, but that's OK because we do
all admin on the server and we don't want it browsable. However, trying
to run http://localhost:9830 on the server itself does show the main page,
I have already looked at this and the configuration looks proper.. That
is why I posted the search results to start. , To show this is what I've
already done.. I have restarted the directory server also.
On 4/23/2014 3:02 PM, Matthew Schmitt wrote:
On 04/23/2014 01:03 PM, harry.dev...@faa.gov wrote:
OK, I may have spoken a bit too soon. The reason I can't browse to it
is because of our firewall. We block port 9830, but that's OK because
we do all admin on the server and we don't want it browsable.
However, trying to run
