ENVIRONMENT.D(5)                environment.d               ENVIRONMENT.D(5)

NAME         top

       environment.d - Definition of user session environment

SYNOPSIS         top






DESCRIPTION         top

       The environment.d directories contain a list of "global" environment
       variable assignments for the user environment.
       systemd-environment-d-generator(8) parses them and updates the
       environment exported by the systemd user instance to the services it

       It is recommended to use numerical prefixes for file names to
       simplify ordering.

       For backwards compatibility, a symlink to /etc/environment is
       installed, so this file is also parsed.


       Configuration files are read from directories in /etc/, /run/, and
       /usr/lib/, in order of precedence. Each configuration file in these
       configuration directories shall be named in the style of
       filename.conf. Files in /etc/ override files with the same name in
       /run/ and /usr/lib/. Files in /run/ override files with the same name
       in /usr/lib/.

       Packages should install their configuration files in /usr/lib/. Files
       in /etc/ are reserved for the local administrator, who may use this
       logic to override the configuration files installed by vendor
       packages. All configuration files are sorted by their filename in
       lexicographic order, regardless of which of the directories they
       reside in. If multiple files specify the same option, the entry in
       the file with the lexicographically latest name will take precedence.
       It is recommended to prefix all filenames with a two-digit number and
       a dash, to simplify the ordering of the files.

       If the administrator wants 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. If the vendor configuration file is
       included in the initrd image, the image has to be regenerated.


       The configuration files contain a list of "KEY=VALUE" environment
       variable assignments, separated by newlines. The right hand side of
       these assignments may reference previously defined environment
       variables, using the "${OTHER_KEY}" and "$OTHER_KEY" format. It is
       also possible to use "${FOO:-DEFAULT_VALUE}" to expand in the same
       way as "${FOO}" unless the expansion would be empty, in which case it
       expands to DEFAULT_VALUE, and use "${FOO:+ALTERNATE_VALUE}" to expand
       to ALTERNATE_VALUE as long as "${FOO}" would have expanded to a
       non-empty value. No other elements of shell syntax are supported.

       EachKEY must be a valid variable name. Empty lines and lines
       beginning with the comment character "#" are ignored.

       Example 1. Setup environment to allow access to a program installed
       in /opt/foo



SEE ALSO         top

       systemd(1), systemd-environment-d-generator(8),

COLOPHON         top

       This page is part of the systemd (systemd system and service manager)
       project.  Information about the project can be found at 
       ⟨⟩.  If you have a bug
       report for this manual page, see 
       ⟨⟩.  This
       page was obtained from the project's upstream Git repository 
       ⟨⟩ on 2017-03-13.  If you dis‐
       cover any rendering problems in this HTML version of the page, or you
       believe there is a better or more up-to-date source for the page, or
       you have corrections or improvements to the information in this
       COLOPHON (which is not part of the original manual page), send a mail

systemd 233                                                 ENVIRONMENT.D(5)