Environment variables: Difference between revisions
imported>Yuu No edit summary |
imported>Yuu No edit summary |
||
| Line 21: | Line 21: | ||
} | } | ||
</syntaxhighlight> | </syntaxhighlight> | ||
= Troubleshooting = | |||
== sudo[3424]: pam_env(sudo:session): Expandable variables must be wrapped in {} <$ENVIRONMENT_VARIABLE/path/to> - ignoring == | |||
=== Description === | |||
Error logs may be found with <code>journalctl -xb -p3</code> regarding the no presence of curly braces <code>{}</code> for variable expansion. | |||
<syntaxhighlight lang="shell"> | |||
sudo[3424]: pam_env(sudo:session): Expandable variables must be wrapped in {} <$ENVIRONMENT_VARIABLE/path/to> - ignoring | |||
<syntaxhighlight lang="shell"> | |||
While checking the configuration values, for instance with <code>nixos-option environment.sessionVariables</code>, it might be found that Nix is correctly parsing the curly braces. | |||
<syntaxhighlight lang="nix"> | |||
Value: | |||
{ | |||
... | |||
ENVIRONMENT_VARIABLE = "${ENVIRONMENT_VARIABLE}/path/to"; | |||
... | |||
} | |||
<\syntaxhighlight> | |||
This indicates that the curly braces are getting removed at a later stage. | |||
=== Solution or workaround === | |||
Unknown. | |||