Skip to main content
Unix & Linux

Return to Answer

Improved markup, clarified numbered list of steps
Source Link
edit approved Feb 29, 2020 at 20:55
celadon
edit approved Feb 29, 2020 at 20:55
celadon
  • 117
  • 9

The /etc/profile/etc/profile file contains system wide profile settings. Within that file, many distributions are sourcing scripts within /etc/profile.d/ /etc/profile.d. Hence, all interactive logins will invoke what is in that folder. If you want a profile script to be scoped to one account, you have to either 1) move that script into ~/.profile or ~/.bash_profile (for bash users), or 2) add login in the vk.sh to skip execution based on the logged in user.

  1. move that script into ~/.profile or ~/.bash_profile (for bash users), or

  2. add login in the vk.sh to skip execution based on the logged in user.

The /etc/profile file contains system wide profile settings. Within that file, many distributions are sourcing scripts within /etc/profile.d/ . Hence, all interactive logins will invoke what is in that folder. If you want a profile script to be scoped to one account, you have to either 1) move that script into ~/.profile or ~/.bash_profile (for bash users), or 2) add login in the vk.sh to skip execution based on the logged in user.

The /etc/profile file contains system wide profile settings. Within that file, many distributions are sourcing scripts within /etc/profile.d. Hence, all interactive logins will invoke what is in that folder. If you want a profile script to be scoped to one account, you have to either

  1. move that script into ~/.profile or ~/.bash_profile (for bash users), or

  2. add login in the vk.sh to skip execution based on the logged in user.

Source Link
Iyad K
Iyad K
  • 231
  • 2
  • 3

The /etc/profile file contains system wide profile settings. Within that file, many distributions are sourcing scripts within /etc/profile.d/ . Hence, all interactive logins will invoke what is in that folder. If you want a profile script to be scoped to one account, you have to either 1) move that script into ~/.profile or ~/.bash_profile (for bash users), or 2) add login in the vk.sh to skip execution based on the logged in user.