Bug 36325 - Make NETWORK_TIMEOUT in ldap.conf configurable (2.0)
Make NETWORK_TIMEOUT in ldap.conf configurable (2.0)
Product: Univention Corporate Client (UCC)
Classification: Unclassified
Component: General
Other Linux
: P5 normal
: UCC 2.0-errata
Assigned To: Erik Damrose
Moritz Muehlenhoff
Depends on:
  Show dependency treegraph
Reported: 2014-10-28 10:38 CET by Michael Grandjean
Modified: 2014-12-08 12:45 CET (History)
2 users (show)

See Also:
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?:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Note You need to log in before you can comment on or make changes to this bug.
Description Michael Grandjean univentionstaff 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 univentionstaff 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 univentionstaff 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 univentionstaff 2014-12-08 12:45:45 CET