On 06/07/2016 12:35 PM, Job Cacka wrote:
It looks like 6.7 has 389-ds-base-1.2.11.15-68.el6_7.src.rpm available, but that isn't 70.
Hmmm, -70 came out as an errata update for 6.7 (but you need to be a
paying customer to get that). If you are using centOS it will
eventually be released for everyone but I can't comment on what/when
they(centOS) will do it.
I think the fix is simple enough there is probably not enough pain to warrant changing. Could making certain changes in the 389 console windows client be equivalent to the ldapmodify command used to in the bug?
No. And gidNumber is a single valued attribute, so it actually does not
fall victim to this bug. So either the attribute index was simply never
"indexed" initially, or there is a some unknown bug that corrupts
indexes. I don't see how rebooting a system can impact database files,
so I think that was just a coincidence.
Regards,
Mark
Thanks,
Job
--
389-users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://lists.fedoraproject.org/admin/lists/389-users@xxxxxxxxxxxxxxxxxxxxxxx
--
389-users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://lists.fedoraproject.org/admin/lists/389-users@xxxxxxxxxxxxxxxxxxxxxxx
