Public bug reported:
Whatever client and from whatever system (I use connectbot from my G1
phone and putty from windows) the ~/.bashrc file is never automatically
processed. I have to manually run:
source ~/.bashrc
and then everything is as it should be.
a...@fileserver:~$ ls -la ~/.bashrc
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33113420/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/33113421/XsessionErrors.txt
--
Always need to run: source ~/.bashrc
https://bugs.launchpad.net/bugs/54
You received this
Even from windows clients via putty?
--
Always need to run: source ~/.bashrc
https://bugs.launchpad.net/bugs/54
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
--
Ubuntu-server-bugs mailing list
a...@fileserver:~$ ls .bash*
.bash_history .bashrc
From the local machine:
a...@fileserver:~$ ps $$
PID TTY STAT TIME COMMAND
5303 pts/0Rs 0:00 [bash]
I will run the same command BEFORE running: source ~/.bashrc from the
remote system and provide the output.
From G1 phone using connectbot:
a...@fileserver:~$ ps $$
PID TTY STAT TIME COMMAND
25803 pts/1 Rs 0:00 -bash
and is same after running: source ~/.bashrc
May affect it but I reduced the number of ttys to 2 instead of keeping
the usual 6 that come as part of a stock install. Would this affect
By jove he cracked it. Lack of ~/.profile screwing things up. Copied
/etc/skel/.profile and was fine and dandy
Thanks a wole lot Achim. Good work :D
--
Always need to run: source ~/.bashrc
https://bugs.launchpad.net/bugs/54
You received this bug notification because you are a member of
