FS#49320 - [pam] Set basic environment variables in /etc/environment, not (just) in /etc/profile
Attached to Project:
Arch Linux
Opened by Sander Maijers (sanmai-NL) - Friday, 13 May 2016, 10:39 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 20 September 2023, 03:10 GMT
Opened by Sander Maijers (sanmai-NL) - Friday, 13 May 2016, 10:39 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 20 September 2023, 03:10 GMT
|
Details
When the user changes his/her shell on current Arch Linux to
one doesn't/cannot read /etc/profile (e.g. fish), the base
PATH environment variable won't be set correctly without
tricks.
Actual behavior: PATH is now only set in /etc/profile (with filesystem 2015.09-1) and not in /etc/environment (with pam 1.2.1-3). Desired behavior: Why is e.g. PATH not (also) in /etc/environment? Suppose you want to keep something like PATH="/usr/local/sbin:/usr/local/bin:/usr/bin" around in /etc/profile, any shell that does read /etc/profile could still process /etc/profile.d as before, setting the base PATH conditional on PATH it being set already, using PATH="${PATH:-/usr/local/sbin:/usr/local/bin:/usr/bin}" |
This task depends upon
Closed by Toolybird (Toolybird)
Wednesday, 20 September 2023, 03:10 GMT
Reason for closing: Won't implement
Additional comments about closing: No interest from PM's. Setting up fish is covered in the wiki.
Wednesday, 20 September 2023, 03:10 GMT
Reason for closing: Won't implement
Additional comments about closing: No interest from PM's. Setting up fish is covered in the wiki.
FS#47884.