UCS 2.4 - Univention

9 Desktop systems
• If files are added, these files are copied into the user’s home directory at the next user log-in. If files
with the same name already exist, these will be overwritten.
• If a file is removed and the user has not made any amendments to this file in his home directory, it
will be removed.
• If a file is removed and the user has made amendments to this file in his home directory, it will not
be removed.
• If the user amends files created by univention-skel, these amendments remain unchanged at later
log-ins. If a user deletes files, there are recreated at the next log-in.
Files are created with 0600 permissions and directories with 0700 as default. These default values can
be changed with the Univention Configuration Registry variable skel/permissions/directory or the
Univention Configuration Registry variable skel/permissions/file.
To adapt newly created directories or files subsequently (e.g., file permissions), the possibility exists of
storing a script below /etc/univention/skel.meta/.
For example, the script /etc/univention/skel.meta/.bashrc can be created to amend the
file .bashrc subsequently. If the directory .emacs needs to be modified subsequently, a
/etc/univention/skel.meta/.emacs/.directory can be created.
9.6.3 Setting environment variables
If environment variables need to be set for users which are valid for the whole KDE session and amongst
other things can be used in KDE desktop profiles (see following section), this can be done via entries in the
file /home//.univention-environment. For example, the following entry must be made in
this file to set the variable $KOLABSERVER to ugs-server01.company.com for the whole KDE session:
export KOLABSERVER=ugs-server01.company.com
For users who already have a home directory, this must be entered in
/home//.univention-environment. To incorporate this for all new users, this file can
be stored under /etc/univention/skel/ accordingly.
9.7 Global home directories
For managed and mobile clients, home directories are automatically created and used on the local hard-
drive as standard. This has the disadvantage that user settings and files can only be saved on the client
currently being used and are not available for log-ins on another client.
It poses a possible problem for thin clients that by default the home directory is used on the terminal server
on which the terminal session was started. If more than one terminal server is available, however, the
log-in occurs randomly on one of the systems and the respective local home directory is used.
To have uniform home directories across all clients, global home directories must be used. These direc-
tories are saved on a shared server on which all the clients are mounted, and which are thus accessible
from every client. However, in this case, it must be noted that these home directories are not available for
managed and mobile clients when there is no connection to the shared server.
216