[XCSSA] Pecular bash login problem

[xcssa@xcssa.org]

Yes. At first I thought it was a $PATH issue so I added the /bin,
/usr/bin, /usr/sbin to his path, but that didn't work.

# .bash_profile

# Get the aliases and functions
if [ -f ~/.bashrc ]; then
        . ~/.bashrc
fi

# User specific environment and startup programs

PATH=$PATH:$HOME/bin:/bin:/usr/bin:/usr/sbin:/usr/local/bin

export PATH
unset USERNAME


On 5/17/06, xcssa-admin@xcssa.org <xcssa-admin@xcssa.org> wrote:
> Does this user have a ~/.bash_profile file?
> -Kevin
>
> xcssa-admin@xcssa.org wrote:
> > The env shows the users .bashrc environment variables after logging
> > in. It seems like when they log in nothing is being parsed until after
> > logging in. As for Bruce's statement about /etc/profile, the thing is,
> > if that file is bad wouldn't I expect this logging problem for all
> > users?
> >
> >
> > On 5/17/06, xcssa-admin@xcssa.org <xcssa-admin@xcssa.org> wrote:
> >> 1. What does the "env" command show you upon logging in?
> >>   (or is the login itself actually failing?
> >>    if so: are there any clues in /var/log/?
> >>           can they scp?
> >>           is rlogin/ftp/telnet available?
> >>      i.e. does it matter what program is being used for the login?)
> >> 2. After you login can you source the .bashrc file without errors?
> >> 3. What does the "env" command show you after sourcing .bashrc?
> >>
> >> Wierd.
> >>
> >> My .02,
> >> -Kevin
> >>
> >> On Tue, 2006-05-16 at 17:09 -0500, xcssa-admin@xcssa.org wrote:
> >> > I think I have stumbled on the strangest login error. Out of 100s of
> >> > users, I have one user that has this problem. When they try to SSH
> >> > into the main computer they get this error:
> >> >
> >> > -bash: id: command not found
> >> > -bash: [: =: unary operator expected
> >> > -bash: id: command not found
> >> > -bash: dircolors: command not found
> >> > -bash: grep: command not found
> >> > -bash: grep: command not found
> >> > -bash: id: command not found
> >> > -bash: [: =: unary operator expected
> >> > -bash: id: command not found
> >> > -bash: id: command not found
> >> > -bash: id: command not found
> >> > -bash: [: too many arguments
> >> >
> >> > At first I thought it was a bad .bashrc or .bash_profile file so I
> >> > moved everything .bash, .csh, .profile to a temp directory and tried
> >> > to ssh in, same problem. I have now tracked it down to the first 3
> >> > lines come from /etc/bashrc, the rest come from profile.d files in
> >> > /etc/profile.d. I would suspect that if those were corrupt or wrong,
> >> > all of my users would experience this problem.
> >> >
> >> > One other thing, their home directory is NFS mounted from their
> >> > workstation. I have another user with the exact setup (NFS'ed home)
> >> > that I setup this morning thinking he would have the same problem too
> >> > (maybe something with NFS), but nope, his ssh sessions work just fine.
> >> >
> >> > Any ideas guys/gals?
> >> >
> >> > System - CentOS 4.2
> >> >
> >> >
> >>
> >> _______________________________________________
> >> XCSSA mailing list
> >> XCSSA@xcssa.org
> >> http://xcssa.org/mailman/listinfo/xcssa
> >>
> >
> >
>
> _______________________________________________
> XCSSA mailing list
> XCSSA@xcssa.org
> http://xcssa.org/mailman/listinfo/xcssa
>


-- 
Jeremy