Why is bash profile not sourced for remote SSH?
That difference in terminal behavior between local and remote connections is what I consider a bug in VS Code’s remote ssh implementation. When VS Code makes it’s initial ssh connection to the host, .bash_profile is sourced (as per a login shell), however any/all interactive terminals brought up in VS Code source .bashrc
Which is the latest version of VS Code bash profile?
Version was 1.38.1 When VS Code makes it’s initial ssh connection to the host, .bash_profile is sourced (as per a login shell), however any/all interactive terminals brought up in VS Code source .bashrc Any/all interactive terminals brought up source .bash_profile (as per a login shell)
Which is ssh command will start a login shell?
In other words, if the ssh command only has options (not a command), like: It will start a login shell, a login shell reads ~/.bash_profile. An ssh command which does have a command, like: Where the command is : (or do nothing). It will not start a login shell, therefore ~/.bashrc is what will be read.
Why does remote Bash terminal only source bashrc?
Not sure if this is “as intended” or not, but remote bash terminals (when connected via SSH) only seem to source .bashrc and not .profile (like a typical login shell would). Obviously not the end of the world, but still curious. 🙂 Local dev w/ bash terminal seems to source .profile.
Why is Bash source not working in CentOS 7?
I have a file to be sourced in Centos 7. It just works fine if I do : however, if I put this in a shell script, it doesn’t work.. can anyone tell me what I might be doing wrong, or missing? source is a command implemented in bash, but not in sh. There are multiple ways to fix your script. Choose either one.
How to change the source of a bash script?
You can also change the source with a dot command which does the same thing but is supported in both bourne and bash. Now the script will work with either sh or bash. You should also run the script directly to avoid confusions like these by making it executable chmod +x xRUN, and invoking it like this: