I have a
.bash_profile in my home directory, but it isn't getting run on login. If I do the following, then things seem to be as I expect:
ssh myhost bash source ~/.bash_profile
But normally that all happens on login. Thoughts?
Super User is a question and answer site for computer enthusiasts and power users. It only takes a minute to sign up.Sign up to join this community
On top of akira's answer, you can also edit your /etc/passwd file to specify your default shell.
You will find a line like this example:
The shell is specified at the end.
You might check your terminal program. It might be configured to run /bin/sh rather than /bin/bash
Bash executes .bash_profile only for login sessions. .bashrc is executed for all bash sessions, not only login sessions. Try sourcing .bash_profile from .bashrc (avoid circular dependency!) or configuring your terminal program to run /bin/bash -l as a shell program.
To make any shell your default, first verify it is installed and recognized on your computer by looking at the contents of
$ cat /etc/shells # /etc/shells: valid login shells /bin/sh /bin/bash /usr/bin/bash /bin/rbash /usr/bin/rbash /bin/dash /usr/bin/dash /usr/bin/fish
chsh to change your shell:
$ sudo chsh -s /usr/bin/bash $(whoami) # or sudo chsh -s /bin/bash $(whoami)
One alternative is to rename your startup script into .profile. This file is being source by most Unix shells.
If you somehow don't see your username in the /etc/passwd file [this is the case when your system is under control of some other domain e.g. in IT companies]
Or it says "user not found" with
chsh option than below process might help you.
The logic behind the below trick -> On Ubuntu, /bin/sh is dash. You can switch your system to using bash. On Ubuntu, /bin/sh is a symbolic link to dash. You can make it a symbolic link to bash instead.To change it, run
sudo dpkg-reconfigure dash
And press No to switch to bash.
Now, go to Terminal->Edit->preferences->Command and tick the checkbox with statement
Run command as login shell
And that's it.
There's not enough information in your question for me to say for sure, but I've hit the same problem before. Assuming you've already get /bin/bash set in your password entry, it may be the way your terminal launches.
If you're trying to launch a GUI terminal, say
gnome-terminal you may be expecting the shell to read your bash startup files. However, this doesn't happen on Ubuntu and maybe other systems by default.
The way I've fixed it on Ubuntu is to edit the gnome-terminal preferences, and set the startup command to be
-l is short for
--login. This tells bash to startup as as login shell, which causes it to load the startup scripts as you get when logging in via ssh.
I'm sure there's a good rationale for this being the way it is, but I found it surprising and a more than a bit annoying as I share the same profiles across linux, cywgin and macos systems.
I had this same error, and the above answers did not work for me. For some reason my shell was still loading as just
/bin/sh instead of
/bin/bash and I have the command to in my
.profile as it is supposed to be in Ubuntu 16.04 but I also have a blank
.bash_profile file that appears to be being read by
.bashrc instead of
So to get everything to work I simply added the command I needed to launch into my
.bash_profile file and then everything worked on next ssh.
So I would say if you have all three files:
.profile make sure your
.bash_profile file has stuff in it you want to load on login to the shell environment.