From: Niall O Broin (nobroin at domain sced.esoc.esa.de)
Date: Thu 23 Sep 1999 - 08:13:02 IST
Alan Sobey said
>
> Anyway, what I was going to ask is can anyone think why ~/.bashrc (which
> simply calls /etc/bashrc) would fail to execute _only_ when telneting in?
> It works fine if I log in locally and runs fine with . ~/.bashrc but not
> ~/.bashrc as below:
>
> [alan at domain carmen alan]$ ~/.bashrc
> bash: /home/users/alan/.bashrc: Permission denied
> [alan at domain carmen alan]$ . ~/.bashrc
> [alan at domain carmen alan]$
> <works fine and processes /etc/bashrc>
>
> Permissions are
> -rw-r--r-- 1 alan users 140 Sep 22 16:17 .bashrc
>
Your .bashrc is 140 bytes long. This is way too long to simply be executing
/etc/bashrc - let's have a look at it. Also let's see your ~/.bash_profile
and it mightn't be a bad idea if you RTFM re bash and specifically the
INVOCATION section - you might even figure the problem out yourself then :-)
I know I've had oddball issues with bash startup before, and it's always been
due to an inexact appreciation of the interaction between ~/.bashrc, ~/.profile,
~/.bash_login, ~/.bash_profile and /etc/profile. Note that bash itself doesn't
care about /etc/bashrc or /etc/Bashrc or whatever - if you source anything from
/etc at shell start other than /etc/profile it's because of something you do,
and not bash itself. BTW it's nothing to do with your .bashrc permissions - that
file should be owned by you and be readable - nothing else is needed but won't
have any impact anyway.
Kindest regards,
Niall O Broin
UNIX Network Administrator nobroin at domain esoc.esa.de
Ground Systems Engineering Department Ph./Fax +49 6151 90 3619/2179
European Space Operations Centre, Darmstadt, Germany
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:04:35 GMT