Thanks for the swift response - size depends on the success of the project - am tempted to go with external config directory assuming I can get it working...I tried to the procedure I listed below i.e. installed the RPM, ran setup to create a 'dsconfig' instance on port 5555.Then I created a master.inf file for inputing into the ds_newinst.pl script:[General]FullMachineName= server1.jamesd.comSuiteSpotUserID= ldapServerRoot= /opt/fedora-dsConfigDirectoryAdminID= adminConfigDirectoryAdminPwd= blahConfigDirectoryLdapURL= ldap://server1.jamesd.com:5555/o=NetscapeRootAdminDomain= jamesd.com[slapd]ServerPort= 389ServerIdentifier= master01Suffix= dc=jamesd,dc=comRootDN= cn=Directory ManagerRootDNPwd= blahUserExistingMC=1When I ran that it seemed to work - instance called master01 was created and is running.When running the console though, it's not listed - only the Administration Server and 'dsconfig' Directory Server instance. How can I make the master01 instance appear in the admin console and also verify that master01 is using dsconfig to stores is configuration data?Thanks again> Date: Thu, 26 Jul 2007 09:33:37 -0600> From: rmeggins at redhat.com> To: fedora-directory-users at redhat.com> Subject: Re: Configuration Directory Question> > James Deuchar wrote:> > Hi,> >> > I've got a what I thought was a relatively simple DS setup with two > > master DS servers doing master-master replication. In the future > > slaves may be added into the equation.> >> > Initially I installed both servers the same - as standalone DS' each > > with it's own admin server and 'in-house' o=NetscapeRoot configuration > > directory.> >> > Reading some of the Redhat docs on 'Configuration decisions' it talks > > about having the configuration directory in a separate directory > > instance - based on what I've seen from the DS setup script this > > implies supplying those details during the install of the real DS > > instances that will contain the data.> >> > Is my understanding correct? Does this mean I should be installing an > > independent configuration directory on both masters and setup > > replication between them to provide a redundant configuration > > directory alongside the redundant data directories?> For small deployments, you can have your config DS and data DS be the same.> >> > If so is the install procedure reasonable?:> >> > - install fedora RPM on server 1> > - Run setup script to create server 1 config directory> > - Run ds_newinst.pl to create data directory on the same server > > pointing it to the local config directory during setup> > - Repeat on server 2> > - Setup replication on data masters and on config directories> Sure.> >> > Many thanks!> >> > ------------------------------------------------------------------------> > Are you the Quizmaster? Play BrainBattle with a friend now! > > <http://specials.uk.msn.com/brainbattle>> > ------------------------------------------------------------------------> >> > --> > Fedora-directory-users mailing list> > Fedora-directory-users at redhat.com> > https://www.redhat.com/mailman/listinfo/fedora-directory-users> > > _________________________________________________________________ Feel like a local wherever you go with BackOfMyHand.com http://www.backofmyhand.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.fedoraproject.org/pipermail/389-users/attachments/20070726/c0c2dd03/attachment.html
