1HOMED.CONF(5)                     homed.conf                     HOMED.CONF(5)
2
3
4

NAME

6       homed.conf, homed.conf.d - Home area/user account manager configuration
7       files
8

SYNOPSIS

10       /etc/systemd/homed.conf
11
12       /etc/systemd/homed.conf.d/*.conf
13
14       /run/systemd/homed.conf.d/*.conf
15
16       /usr/lib/systemd/homed.conf.d/*.conf
17

DESCRIPTION

19       These configuration files control default parameters for home
20       areas/user accounts created and managed by systemd-homed.service(8).
21

CONFIGURATION DIRECTORIES AND PRECEDENCE

23       The default configuration is set during compilation, so configuration
24       is only needed when it is necessary to deviate from those defaults.
25       Initially, the main configuration file in /etc/systemd/ contains
26       commented out entries showing the defaults as a guide to the
27       administrator. Local overrides can be created by editing this file or
28       by creating drop-ins, as described below. Using drop-ins for local
29       configuration is recommended over modifications to the main
30       configuration file.
31
32       In addition to the "main" configuration file, drop-in configuration
33       snippets are read from /usr/lib/systemd/*.conf.d/,
34       /usr/local/lib/systemd/*.conf.d/, and /etc/systemd/*.conf.d/. Those
35       drop-ins have higher precedence and override the main configuration
36       file. Files in the *.conf.d/ configuration subdirectories are sorted by
37       their filename in lexicographic order, regardless of in which of the
38       subdirectories they reside. When multiple files specify the same
39       option, for options which accept just a single value, the entry in the
40       file sorted last takes precedence, and for options which accept a list
41       of values, entries are collected as they occur in the sorted files.
42
43       When packages need to customize the configuration, they can install
44       drop-ins under /usr/. Files in /etc/ are reserved for the local
45       administrator, who may use this logic to override the configuration
46       files installed by vendor packages. Drop-ins have to be used to
47       override package drop-ins, since the main configuration file has lower
48       precedence. It is recommended to prefix all filenames in those
49       subdirectories with a two-digit number and a dash, to simplify the
50       ordering of the files.
51
52       To disable a configuration file supplied by the vendor, the recommended
53       way is to place a symlink to /dev/null in the configuration directory
54       in /etc/, with the same filename as the vendor configuration file.
55

OPTIONS

57       The following options are available in the [Home] section:
58
59       DefaultStorage=
60           The default storage to use for home areas. Takes one of "luks",
61           "fscrypt", "directory", "subvolume", "cifs". For details about
62           these options, see homectl(1). If not configured or assigned the
63           empty string, the default storage is automatically determined: if
64           not running in a container environment and /home/ is not itself
65           encrypted, defaults to "luks". Otherwise defaults to "subvolume" if
66           /home/ is on a btrfs file system, and "directory" otherwise. Note
67           that the storage selected on the homectl command line always takes
68           precedence.
69
70       DefaultFileSystemType=
71           When using "luks" as storage (see above), selects the default file
72           system to use inside the user's LUKS volume. Takes one of "btrfs",
73           "ext4" or "xfs". If not specified defaults to "btrfs". This setting
74           has no effect if a different storage mechanism is used. The file
75           system type selected on the homectl command line always takes
76           precedence.
77

SEE ALSO

79       systemd(1), systemd-homed.service(8)
80
81
82
83systemd 254                                                      HOMED.CONF(5)
Impressum