Hi Steven,
thanks for reporting this, I created a Bugzilla for the doc:
https://bugzilla.redhat.com/show_bug.cgi?id=824768
Martin
On Thu, 2012-05-24 at 04:26 +, Steven Jones wrote:
Hi,
Page 381 section 18.7.2 says,
ipa replica-manage connect srv2.example.com srv4.example.com
when
On Thu, 2012-05-24 at 05:50 +, Steven Jones wrote:
Hi,
Just windering but I thought that whether I did change son the
original master, or on the replica that changes would flow to the
other both ways? or do changes only flow original master to replica?
Since we use multi-master
On Wed, 2012-05-23 at 19:27 -0400, Dmitri Pal wrote:
On 05/23/2012 05:40 PM, Jan-Frode Myklebust wrote:
We have quite strict firewalls, so I need to specify the IPA network
ports accurately. So, we have now opening for:
80/tcp, 88/tcp, 389/tcp, 443/tcp, 464/tcp, 636/tcp
88/udp,
On Thu, May 24, 2012 at 10:50:23AM +0200, Martin Kosek wrote:
I suppose you don't need to open 7389/tcp for all clients unless you
want them to be able to run LDAP search against dogtag backend LDAP
database.
I don't see why I would want that, so I'll just open it between the
ipa-servers for
Gelen James wrote:
Hi all,
Could FC16 installed FreeIPA 2.2.0? the freeIPA site said that FC16 has
some underlying dependencies.
It is possible to build it and install in F-16 but you'll have SELinux
problems.
rob
___
Freeipa-users mailing list
On 05/17/2012 10:47 AM, Lucas Yamanishi wrote:
On 05/17/2012 09:34 AM, Rob Crittenden wrote:
Lucas Yamanishi wrote:
Hi everybody,
I've added some custom schema to my directory, but it's useless to me if
if I can't control read permissions on it. This is obviously a little
tricky since
On 05/16/2012 06:20 AM, Sumit Bose wrote:
On Tue, May 15, 2012 at 09:05:43AM -0700, Gelen James wrote:
Hi Sumit,
Thanks for your quick reply.
In the chapter
