linux_bash_rcprofile.md

• Zsh/Bash startup files loading order (.bashrc, .zshrc etc.)
• Another solution: bash profile works for user but not sudo

Zsh/Bash startup files loading order (.bashrc, .zshrc etc.)

/bin/bash
       The bash executable
/etc/profile
       The systemwide initialization file, executed for login shells
~/.bash_profile
       The personal initialization file, executed for login shells
~/.bashrc
       The individual per-interactive-shell startup file
~/.bash_logout
       The individual login shell cleanup file, executed when a login shell exits
~/.inputrc
       Individual readline initialization file

---

• ~/.bash_profile is only sourced by bash when started in login mode.
  • That is typically when you log in at the console (Ctrl+Alt+F1..F6),
  • connect via ssh,
  • or use sudo -i or su - to run commands as another user.
• When you log in graphically(under X), ~/.profile will be specifically sourced by the script that launches gnome-session (or whichever desktop environment you're using)
  • So ~/.bash_profile is not sourced at all when you log in graphically.
• When you open a terminal, the terminal starts bash in ( non-login ) interactive mode,
  • which means it will source ~/.bashrc.

---

Generally,

• For bash, put stuff in ~/.bashrc, and make ~/.bash_profile source it.
  • For stuff like https proxy, put it in /etc/bashrc so as to sudo can access those setting as well.
• For zsh, put stuff in ~/.zshrc, which is always executed.

Another solution: bash profile works for user but not sudo

sudo vi /etc/sudoers

• replace
  • Defaults env_reset with
  • Defaults env_keep += "PATH http_proxy https_proxy no_proxy"