Gerrard Geldenhuis wrote:
> -----Original Message-----
> From: 389-users-bounces(a)lists.fedoraproject.org [mailto:389-users-
> bounces(a)lists.fedoraproject.org] On Behalf Of Rich Megginson
> Sent: 10 November 2010 14:26
> To: General discussion list for the 389 Directory server project.
> Subject: Re: [389-users] upgrading packages
>
> Angel Bosch Mora wrote:
>
>> hi,
>>
> In general, it can't. The reason is that you may be using a centralized
> configuration directory server to manage several hosts with one 389-
> console. If you do that, the data that needs to be updated is on the remote
> server which hosts the configuration directory server (the one with the
> o=NetscapeRoot suffix). We need to get at least the console admin
> password to update that information remotely.
>
>> - does it matter how many instances are configured?
>>
Is "admin server" and "centralized configuration directory" the same
thing here?
No. The configuration directory server is the directory server that has
the o=NetscapeRoot suffix. The admin server is the http(s) agent
running on each machine that handles console authentication and access,
and runs CGI programs.
I am slightly confused about this. I thought that you had to have a
admin server for each physical hosts?
Yes.
Regards
[Gerrard Geldenhuis]
________________________________________________________________________
In order to protect our email recipients, Betfair Group use SkyScan from
MessageLabs to scan all Incoming and Outgoing mail for viruses.
________________________________________________________________________
--
389 users mailing list
389-users(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users