Also check that the user's shell in /etc/passwd in explicitly /bin/bash.
If it is /bin/sh, bash still gets run, but the behavior is a little
different as it tries to stay compatibile with the sh's of old. One of
the differences is that it doesn't read .bashrc (or, .bash_profile
either, IIRC).
Bill
On Mon, 2002-04-01 at 19:35, Mario Lombardo wrote:
> Hmm, well root is exporting it's .bashrc, but it's not logged in and
> I'm not picking up any of those settings anyway even with it being
> logged in.
>
> Yes, the user has RW access to its .bashrc file. Yep, I'm aware of
> the command line for this, but I want it to parse this file and
> accept my changes--saving me typing.
>
> I didn't know about the relationship between .bash_profile and
> .bashrc; interesting. I'm pretty sure it's not parsing the .bashrc
> file because I'm able to type the exact alias I want in the command
> line and verify it.
>
> Mario
>
> >Mario:
> >Does the user have read access for the .bashrc file? Also you can set an
> >alias from the command by doing alias = 'rm ' or what ever the above
> >alias will remove the prompt to erase each file. You will also want to
> >add it to the .bash_profile which is read each time the user logs on and
> >the .bashrc is read each time a new shell is started. You can also export
> >the alias to make it global.
> >Mike M
> >
> >Mario Lombardo wrote:
> >
> >> I want this to work in one of my user's .bashrc files:
> >> alias l='ls -lAF --color=auto'
> >>
> >> I 'su root' and after I change the file and save it, I exit su and
> >> exit the user account and log back in as the user, but the settings
> >> won't work, yet I verify the changes took place in .bashrc. What's
> >> going on?
> >>
> >> Also, are users able to run alias at the command prompt? Usually
> >> running this command alone will give all of the currently set aliases.
> >>
> >> Mario
>
>
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 19:35:05 EDT