--On Thursday, September 05, 2013 1:11 PM -0400 Justin Edmands
shockwav...@gmail.com wrote:
Hey,
Certainly new to migrations of LDAP. I migrated our old setup from
OpenLDAP to 389 Directory Server. When using the id command on an LDAP
client, it only returns uid,gid, and one group. It for
Hey,
Certainly new to migrations of LDAP. I migrated our old setup from OpenLDAP
to 389 Directory Server. When using the id command on an LDAP client, it
only returns uid,gid, and one group. It for some reason does not show all
of the actual groups that the user is associated with. What is set to
Hi,
Is there a way to log the time each operation took?
I have strange CPU load (~200%) with just ~15 operations per second.
SRCH is 90% of all operations. All attributed involved in search a
indexed (many single attribute indexes, ~30).
The point is to find which search operations a taking
Justin Edmands wrote:
Hey,
Certainly new to migrations of LDAP. I migrated our old setup from OpenLDAP to
389 Directory Server. When using the id command on an LDAP client, it only
returns uid,gid, and one group. It for some reason does not show all of the
actual groups that the user is
On Thu, Sep 5, 2013 at 1:36 PM, Howard Chu h...@symas.com wrote:
Justin Edmands wrote:
Hey,
Certainly new to migrations of LDAP. I migrated our old setup from
OpenLDAP to
389 Directory Server. When using the id command on an LDAP client, it
only
returns uid,gid, and one group. It for some
--On Thursday, September 05, 2013 9:05 PM +0300 Покотиленко
Костик cas...@meteor.dp.ua wrote:
Hi,
Is there a way to log the time each operation took?
I have strange CPU load (~200%) with just ~15 operations per second.
SRCH is 90% of all operations. All attributed involved in search a
Justin Edmands wrote:
Thank god you got that off of your chest. the solution is:
And OpenLDAP actually has a knowledgeable community that responds to posts,
and gives correct answers.
/etc/sssd/sssd.conf
[domain/default]
..
ldap_group_member = memberUid
You should look
Покотиленко Костик wrote:
Hi,
Is there a way to log the time each operation took?
Every message in syslog already has a timestamp.
Also, recent versions of OpenLDAP include a timestamp on debug output too. You
didn't mention which version you're using so can't tell you much more.
I have
В Чтв, 05/09/2013 в 11:56 -0700, Howard Chu пишет:
Покотиленко Костик wrote:
Hi,
Is there a way to log the time each operation took?
Every message in syslog already has a timestamp.
Every message in syslog has time the operation has finished at. What I
need is the time it took each
В Чтв, 05/09/2013 в 11:35 -0700, Quanah Gibson-Mount пишет:
--On Thursday, September 05, 2013 9:05 PM +0300 Покотиленко
Костик cas...@meteor.dp.ua wrote:
Hi,
Is there a way to log the time each operation took?
I have strange CPU load (~200%) with just ~15 operations per second.
--On Thursday, September 05, 2013 10:58 PM +0300 Покотиленко
Костик cas...@meteor.dp.ua wrote:
В Чтв, 05/09/2013 в 11:35 -0700, Quanah Gibson-Mount пишет:
--On Thursday, September 05, 2013 9:05 PM +0300 Покотиленко
Костик cas...@meteor.dp.ua wrote:
Hi,
Is there a way to log the time each
11 matches
Mail list logo