Arch manual pages

HOMED.CONF(5) homed.conf HOMED.CONF(5)

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





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

The default configuration is defined during compilation, so a configuration file is only needed when it is necessary to deviate from those defaults. By default, the configuration file in /etc/systemd/ contains commented out entries showing the defaults as a guide to the administrator. This file can be edited to create local overrides.

When packages need to customize the configuration, they can install configuration snippets in /usr/lib/systemd/*.conf.d/ or /usr/local/lib/systemd/*.conf.d/. The main configuration file is read before any of the configuration directories, and has the lowest precedence; entries in a file in any configuration directory override entries in the single configuration file. Files in the *.conf.d/ configuration subdirectories are sorted by their filename in lexicographic order, regardless of in which of the subdirectories they reside. When multiple files specify the same option, for options which accept just a single value, the entry in the file with the lexicographically latest name takes precedence. For options which accept a list of values, entries are collected as they occur in files sorted lexicographically.

Files in /etc/ are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages. It is recommended to prefix all filenames in those subdirectories with a two-digit number and a dash, to simplify the ordering of the files.

To disable a configuration file supplied by the vendor, the recommended way is to place a symlink to /dev/null in the configuration directory in /etc/, with the same filename as the vendor configuration file.

The following options are available in the [Home] section:


The default storage to use for home areas. Takes one of "luks", "fscrypt", "directory", "subvolume", "cifs". For details about these options, see homectl(1). If not configured or assigned the empty string, the default storage is automatically determined: if not running in a container environment and /home/ is not itself encrypted, defaults to "luks". Otherwise defaults to "subvolume" if /home/ is on a btrfs file system, and "directory" otherwise. Note that the storage selected on the homectl command line always takes precedence.


When using "luks" as storage (see above), selects the default file system to use inside the user's LUKS volume. Takes one of "ext4", "xfs" or "btrfs". If not specified defaults to "ext4". This setting has no effect if a different storage mechanism is used. The file system type selected on the homectl command line always takes precedence.

systemd(1), systemd-homed.service(8)
systemd 246