I don't think it is a bug. These files were generated during the very large import via ldapadd. The replica files filled the /tmp file system which I believe snowballed into other issues so the replication may not have completed. I was hoping I could configure ADS to use a different location for the replica files. I am also working with our system guys to have the tmp file system increased.
On the note of replication completing. What is the best way to tell the status of replication on ADS? Even getting a count of entries in the database would be helpful. On Mon, Jun 15, 2015 at 9:52 PM, Kiran Ayyagari <[email protected]> wrote: > On Tue, Jun 16, 2015 at 9:31 AM, Ezsra McDonald <[email protected]> > wrote: > > > Greetings > > > > I assume this has to do with the import of 300+k entries to my LDAP. What > > do these mean? Do they have to be in /tmp? Can I put them somewhere else? > > > they are created by the replication subsystem, they are supposed to be > deleted after > use, can you file a bug? > > > > > -rw-r--r-- 1 apacheds apacheds 0 Jun 15 20:32 > > replica2007608221525362157.sorted-data > > -rw-r--r-- 1 apacheds apacheds 0 Jun 15 20:32 > > replica2007608221525362157.sorted-data.db > > -rw-r--r-- 1 apacheds apacheds 685559808 Jun 15 20:45 > > replica2007608221525362157.sorted-data.lg > > > > > > ADS M20 > > > > --Ez > > > > > > -- > Kiran Ayyagari > http://keydap.com >
