Bug 36325

Summary:	Make NETWORK_TIMEOUT in ldap.conf configurable (2.0)
Product:	Z_Univention Corporate Client (UCC)	Reporter:	Michael Grandjean <grandjean>
Component:	General	Assignee:	Erik Damrose <damrose>
Status:	CLOSED FIXED	QA Contact:	Moritz Muehlenhoff <jmm>
Severity:	normal
Priority:	P5	CC:	jmm, steuwer
Version:	unspecified
Target Milestone:	UCC 2.0-errata
Hardware:	Other
OS:	Linux
What kind of report is it?:	---	What type of bug is this?:	---
Who will be affected by this bug?:	---	How will those affected feel about the bug?:	---
User Pain:		Enterprise Customer affected?:
School Customer affected?:		ISV affected?:
Waiting Support:		Flags outvoted (downgraded) after PO Review:
Ticket number:		Bug group (optional):
Max CVSS v3 score:

Description Michael Grandjean

2014-10-28 10:38:16 CET

ldap.conf supports the option "NETWORK_TIMEOUT <integer>". This is really useful for scenarios where the LDAP-server(s) might be (temporarily) unavailable. If NETWORK_TIMEOUT is not set in such a scenario, booting UCC takes ages.

See also Ticket#2014081121000159:
-> UCC boot time lasts up to 10 minutes
-> Specifying "NETWORK_TIMEOUT 2" (seconds) manually in ldap.conf reduces boot time to ~1,5 minutes

See also Bug #31001 for a similar scenario.

Comment 1 Erik Damrose

2014-12-04 14:42:19 CET

The new UCR variable ucc/ldap/network/timeout configures the network timeout, default is 10 seconds.

r56463 univention-ucc-pam 2.0.0-8.45.201412041436
r56464 yaml

Comment 2 Moritz Muehlenhoff

2014-12-05 10:45:58 CET

Ok, NETWORK_TIME can now be configured and uses 10 seconds as a default. YAML file looks fine.

Comment 3 Moritz Muehlenhoff

2014-12-08 12:45:45 CET

http://errata.univention.de/ucc/2.0/4.html