Bug 36352

Summary: Make NETWORK_TIMEOUT in ldap.conf configurable (1.0)
Product: Z_Univention Corporate Client (UCC) Reporter: Moritz Muehlenhoff <jmm>
Component: GeneralAssignee: Erik Damrose <damrose>
Status: CLOSED FIXED QA Contact: Moritz Muehlenhoff <jmm>
Severity: normal    
Priority: P5 CC: grandjean, jmm, steuwer
Version: UCC 1.0   
Target Milestone: UCC 1.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 Moritz Muehlenhoff univentionstaff 2014-10-30 13:39:40 CET
+++ This bug was initially created as a clone of Bug #36325 +++

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 univentionstaff 2014-12-04 15:02:17 CET
The new UCR variable ucc/ldap/network/timeout configures the network timeout,
default is 10 seconds.

r56466 univention-ucc-pam 1.0.2-6.46.201412041449
r56468 yaml
Comment 2 Moritz Muehlenhoff univentionstaff 2014-12-11 12:04:15 CET
Ok, NETWORK_TIME can now be configured and uses 10 seconds as a default. YAML file looks fine.
Comment 3 Moritz Muehlenhoff univentionstaff 2014-12-15 14:45:23 CET
http://errata.univention.de/ucc/1.0/40.html