I'm getting kicked in the ass by syslog when I start using openldap through
nss_ldap (tar, in particular, is deadly; you gotta love the complexity: I run
amanda, which kicks off tar which checks all the UIDs which calls nss_ldap
which calls openldap which calls syslog which uses all the CPU and amanda
takes 3 days to complete). Since the problem is syslog and not openldap per
se, I'm trying to figure out how to make the problem go away.
Since I'm a qmail user, I already have cyclog on my systems, so I'm thinking
about adapting openldap to use it. Before I dig too deep, does anyone have
any experience doing this? "All" I would need is to send the logging info to
stderr instead of calling syslog. How does the -d flag effect the syslogging?
Chris
--
Chris Garrigues virCIO
http://www.DeepEddy.Com/~cwg/ http://www.virCIO.Com
+1 512 432 4046 +1 512 374 0500
4314 Avenue C
O- Austin, TX 78751-3709
My email address is an experiment in SPAM elimination. For an
explanation of what we're doing, see http://www.DeepEddy.Com/tms.html
Nobody ever got fired for buying Microsoft,
but they could get fired for relying on Microsoft.
Attachment:
pgpFIzfjIaiRZ.pgp
Description: PGP signature