Date: Sat, 20 Nov 2004 11:02:39 +0000 From: Dick Davies <rasputnik@hellooperator.net> To: Sean McNeil <sean@mcneil.com> Cc: FreeBSD Current Users <freebsd-current@freebsd.org> Subject: Re: openldap slapd startup delay Message-ID: <20041120110238.GA11995@lb.tenfour> In-Reply-To: <1100723747.18003.4.camel@server.mcneil.com> References: <419B3DA9.8020202@fer.hr> <20041117135058.GB28461@lb.tenfour> <1100723747.18003.4.camel@server.mcneil.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Sean McNeil <sean@mcneil.com> [1136 20:36]: >=20 > Does this fix the start delay, or the problem with stop? I have traced Don't know about a stop problem, I don't see that (but I checkpoint the db fairly often). This cuts the start to about a second. (For some reason if you specify 2 listen sockets that rises to about 8sec, but nothing like the 30+ sec delay (was > 1min on my ME6000 ). > through the start delay and found it is because slapd is opening the > socket and then there is a lookup on group which causes it to try to > read from slapd and you are in a deadlock until the socket times out. > This has always been normal for me (the delay on startup) and others. You mean you store the ldap group as a posixGroup in LDAP? --=20 If we can hit that bull's-eye, the rest of the dominoes will fall like a house of cards... Checkmate! - Zapp. Brannigan Rasputin :: Jack of All Trades - Master of Nuns --PEIAKu/WMn1b1Hv9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (NetBSD) iD8DBQFBnyROVFnamZKfe00RAu7tAJ4uJsjB+dSdzU33+srDEcHwaMpybgCfd7D5 kzvWU4/81QYQvjmrUiU15VQ= =prw3 -----END PGP SIGNATURE----- --PEIAKu/WMn1b1Hv9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041120110238.GA11995>