Bug 35364 - Document fallback UCR variables for thin clients with overlayfs
Document fallback UCR variables for thin clients with overlayfs
Status: CLOSED WONTFIX
Product: Z_Univention Corporate Client (UCC)
Classification: Unclassified
Component: Documentation
unspecified
Other Linux
: P5 normal
: UCC 2.x
Assigned To: Docu maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-07-15 13:04 CEST by Moritz Muehlenhoff
Modified: 2023-06-28 10:32 CEST (History)
0 users

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 Moritz Muehlenhoff univentionstaff 2014-07-15 13:04:17 CEST
In UCR we have two different kinds of variables:

- Locally set variables (/etc/univention/base.conf)
- variables set from a policy (/etc/univention/base-ldap.conf)

On UCC desktop systems or on UCS systems both are stored on persistent storage, i.e. if a system is booted and the retrieval of the LDAP policy isn't possible it can fall back to the values retrieved by the last run.

On UCC thin clients we use an overlayfs. As such the values written to base-ldap.conf are not available on the next reboot.

We should document how to set these "fallback variables":
- For the initial setting see Bug 35363
- The fallback variables to be kept across updates need to be registered in ucc/persistent/ucr.

(Such fallback variables are only relevant for UCC environments where the UCC LDAP server is different from the PXE/DHCP environment)
Comment 1 Philipp Hahn univentionstaff 2023-06-28 10:30:29 CEST
UCC is EoL