Re: [389-users] Announcing 389 Directory Server 1.2.6 Release Candidate 3

Aaron Hagopian wrote: > I filed a bug per Rich: https://bugzilla.redhat.com/show_bug.cgi?id=616206 > > > How did you create the ldif file in > "/var/lib/dirsrv/slapd-/ldif/"? Did you move the ldif > file there from elsewhere on your system? That could explain why > your ldif fil

Re: [389-users] Announcing 389 Directory Server 1.2.6 Release Candidate 3

I filed a bug per Rich: https://bugzilla.redhat.com/show_bug.cgi?id=616206 > How did you create the ldif file in > "/var/lib/dirsrv/slapd-/ldif/"? Did you move the ldif file there > from elsewhere on your system? That could explain why your ldif file ha

Re: [389-users] Announcing 389 Directory Server 1.2.6 Release Candidate 3

On 07/19/2010 08:47 AM, Aaron Hagopian wrote: Ok this time I think I have hit a legit issue with SELinux and 1.2.6 RC3. On my workstation to sync up my ldap server with production I take a ldif dump from production and load it into my system with the ldif2db.pl script. For

Re: [389-users] Announcing 389 Directory Server 1.2.6 Release Candidate 3

I upgraded my fedora 13 x86_64 machine to the RC3 using the rpms in updates-testing and now I cannot start the admin server with selinux enabled. I am attaching the selinux message. It does start when I disable selinux. On Tue, Jul 6, 2010 at 2:38 PM, Rich Megginson wrote: > The 389 team is p

[389-users] Announcing 389 Directory Server 1.2.6 Release Candidate 3

The 389 team is pleased to announce the availability of Release Candidate 3 of version 1.2.6. This release has a few bug fixes. ***We need your help! Please help us test this software.*** It is a release candidate, so it may have a few glitches, but it has been tested for regressions and for ne