Sorry, Bob, it's my bad. ${HOME} in my previous posts were not described
consistently. Actually my $HOME on my office server is "/cis/home/tingli".
"'/cis/home/tingli/bin/bash-3.2.48/bin/bin/bash'" is actually where my new
bash executable lies in the server (the double bins were left from my silly
specification to --prefix when configuring the new bash). I don't have root
privilege to my office server, however I have an office computer that could
load my HOME from the server which seems just like its own hard disk.
My problem is that after I added into .bash_profile:
"SHELL='/cis/home/tingli/bin/bash-3.2.48/bin/bin/bash'
exec $SHELL",
the new bash starts automatically if I ssh to the server from my laptop,
however, if I try to login into my office computer, I will not be able to
with the following error:
"Your session only lasted less than 10 seconds. If you have not logged out
yourself, this could mean that there is some installation problem or that
you may be out of disk space. Try logging in with one of the failsafe
sessions to see if you can fix this problem."
I can login successfully if the line "exec $SHELL" in .bash_profile is
commented. I was wondering if there is some way to make the new bash start
automatically without the login error when loginning into my office
computer?
Thanks!
--
View this message in context:
http://www.nabble.com/Install-Bashdb-and-Bash-not-as-root-tp22316418p22361800.html
Sent from the Gnu - Bash mailing list archive at Nabble.com.
