|
- What is the difference between ~ . profile and ~ . bash_profile?
The original sh sourced profile on startup bash will try to source bash_profile first, but if that doesn't exist, it will source profile Note that if bash is started as sh (e g bin sh is a link to bin bash) or is started with the --posix flag, it tries to emulate sh, and only reads profile Footnotes: Actually, the first one of bash_profile, bash_login, profile See also: Bash
- When exactly do the scripts in etc profile. d get executed?
In etc profile d I got a script called logchk sh which is meant to send an email to the admin email address via bin mail If someone logs in via ssh user@serveradress this script is properly executed and the email is sent However, it depends on the login method if the script is executed or not What works is the following
- profile - Find out what scripts are being run by bash at login - Unix . . .
My terminal starts a login shell, so ~ bash_profile is sourced, followed by ~ profile and ~ bashrc Only in ~ profile do I create the paths entries which are duplicated To be pedantic, this is the order in which the files that SHOULD be sourced are being sourced: Sourced etc profile Sourced etc bash bashrc Sourced bash_profile Sourced
- Colorizing your terminal and shell environment? - Unix Linux Stack . . .
Sure, you can symlink zsh to a file named after any other shell and emulate that shell, but when you do that it doesn't read your bashrc, bash_profile, etc Also, you cannot put emulate bash in your zprofile or zshrc files For anybody who works with advanced features in BASH, there are many subtleties that will bite you BASH is a better sh
- Setting PATH vs. exporting PATH in ~ . bash_profile [duplicate]
What's the difference and which is better to use when customizing my bash profile? Documentation on the export command is scarce, as it's a builtin cmd Excerpt from version 1 of my ~ bash_profil
- How to correctly add a path to PATH? - Unix Linux Stack Exchange
The profile file is read by login shells, so it will only take effect the next time you log in (Some systems configure terminals to read a login shell; in that case you can start a new terminal window, but the setting will take effect only for programs started via a terminal, and how to set PATH for all programs depends on the system )
- What is the purpose of . bashrc and how does it work?
My comment is just a stronger statement of Ilmari Karonen's 2014 comment It is factually incorrect to say " bashrc runs on every interactive shell launch" A login shell is an interactive shell, and it's the counterexample: a login shell does not run bashrc It would be correct to say " bashrc is run by every interactive non-login shell" Bash Reference Manual, section 6 2, "Bash Startup FIles"
- How to permanently set environmental variables
You can add it to the file profile or your login shell profile file (located in your home directory) To change the environmental variable "permanently" you'll need to consider at least these situations:
|
|
|