Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bash not picking up ~/.pam_environment #4782

Closed
clearnote01 opened this issue Dec 23, 2019 · 2 comments
Closed

bash not picking up ~/.pam_environment #4782

clearnote01 opened this issue Dec 23, 2019 · 2 comments

Comments

@clearnote01
Copy link

Steps to reproduce ->

  1. echo "FOO=foo" >> ~/.pam_environment
  2. sudo login
  3. echo $FOO # returns blank; expected output: foo

Use of ~/.pam_environment file?

Suitable files for environment variable settings that should affect just a particular user (rather than the system as a whole) are ~/.pam_environment and ~/.profile. After having edited one of those files, you should re-login in order to initialize the variables.

Windows build number: Microsoft Windows [Version 10.0.19041.1]

@therealkenc
Copy link
Collaborator

image

@alexander-novo
Copy link

Can some light be shed on why this issue is marked as bydesign and closed? How are environment variables meant to be set on WSL?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants