Skip to content

Comments

man: explicitly mention that environment.d/ cannot be used to set the…#29801

Merged
bluca merged 1 commit intosystemd:mainfrom
poettering:man-environment-d-scope-explanation
Nov 1, 2023
Merged

man: explicitly mention that environment.d/ cannot be used to set the…#29801
bluca merged 1 commit intosystemd:mainfrom
poettering:man-environment-d-scope-explanation

Conversation

@poettering
Copy link
Member

… service manager's own env block

Fixes: #29414

@github-actions github-actions bot added the please-review PR is ready for (re-)review by a maintainer label Nov 1, 2023
@bluca bluca merged commit bebf6fc into systemd:main Nov 1, 2023
exclusively the environment blocks passed to the services it manages. Environment variables set that way
thus cannot be used to influence behaviour of the service manager. In order to make changes to the
service manager's environment block the environment must be modified before the user's service manager is
invoked, for example from the system service manager or via a PAM module.</para>
Copy link
Contributor

@rpigott rpigott Nov 3, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@poettering Isn't this false? We have systemd-user.conf(5)'s ManagerEnvironment= setting. Should that be mentioned here?

EDIT: I use this feature with #26675 to set ManagerEnvironment=XDG_CONFIG_DIRS=%h/.hostconfig/%H:/etc/xdg and it does work as intended to extend the user service search path.

@bluca bluca removed the please-review PR is ready for (re-)review by a maintainer label Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

Specifiers in user units don't use environment.d values

3 participants