Bug 29956 - Save boot settings from LDAP
Save boot settings from LDAP
Status: CLOSED WORKSFORME
Product: Z_Univention Corporate Client (UCC)
Classification: Unclassified
Component: General
unspecified
Other Linux
: P5 normal
: UCC 2.0
Assigned To: Erik Damrose
Moritz Muehlenhoff
: interim-2
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-01-08 08:39 CET by Stefan Gohmann
Modified: 2014-06-12 09:19 CEST (History)
1 user (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?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Gohmann univentionstaff 2013-01-08 08:39:14 CET
Currently the UCC client checks the configured boot settings in the LDAP directory and interprets them.

The client should save these settings in UCR otherwise the boot behavior is different depending on whether the LDAP is available or not.
Comment 1 Erik Damrose univentionstaff 2014-04-28 13:33:32 CEST
LDAP Policies are cached locally in /var/cache/ucc/client-policy-$(hostname). The UCR variable grub/append can be used to permanently store boot settings

Thinclients will not update the policy cache on every boot/everytime the policies are queried, but will have the policies cached that were valid during the initial join. I think that this behaviour is OK for thinclients. Thinclients could be mounted read/writeable to update the cache file..
Comment 2 Moritz Muehlenhoff univentionstaff 2014-04-28 15:06:50 CEST
Indeed, this is all covered in UCC 1.0/2.0. (The bug was filed during the UCC 1.0 development cycle)
Comment 3 Moritz Muehlenhoff univentionstaff 2014-06-12 09:19:55 CEST
UCC 2.0 has been released:
 http://docs.univention.de/release-notes-ucc-2.0.html

If this error occurs again, please use "Clone This Bug".