DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:content-type:content-transfer-encoding
	:date:subject:to:message-id:mime-version; q=dns; s=default; b=cC
	O0IWtfeZdE8GmgDdLGUv2Yt8bJA6qmWQKYHspveG8CISbAxz9Gk0oPoCr+XV8YQ5
	NIeK+i2laQPrseif66mO8S0YbRbWDlexuQ768J4Ol3pIGsess1rTfntBewQVIieq
	bKvrL2jTC2srD8kGPdaKG7nFH7nSfDL8PnA0YXfvc=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Denis Excoffier <cygwin@Denis-Excoffier.org>
Content-Type: text/plain; charset=windows-1252
Date: Mon, 16 Jun 2014 22:39:45 +0200
Subject: timeout in LDAP access
To: Cygwin Mailing List <cygwin@cygwin.com>
Message-Id: <F312783D-AD66-4614-922B-E44403C7E372@Denis-Excoffier.org>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
Content-Transfer-Encoding: 8bit

Hello,

I’ve exercised ‘getent' a little bit those days (with 'db_enum: all’ in /etc/nsswitch.conf), and it seems to me
that the timeout ‘tv' (3 seconds, in ldap.cc) is probably too small for servers not so quickly responsive
or with many (500000, fake or real) users around (see the call to ldap_get_next_page_s()). 300 seconds should be
enough i suppose.

Also it is a pity that LDAP_TIMEOUT is not announced to the user (except under strace: 0x55). I don’t know the
general policy for timeouts, but i consider that the user would like to be informed when the passwd/group list was
truncated.

Another (unrelated and less important) problem is that 'getent' happily produces lines with some extra ‘:’, in
particular when the gecos field itself contains ‘:’.

Regards,

Denis Excoffier.
--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple