[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: bash: a: command not found



Kayvan,
If it is "system wide" and sounds like it is,
I'd fire up and xterm and tail -f /var/log/xdm-error.log
and then use another xterm to "telnet localhost" and log in to
see if I got the "bash: a: command not found". If so, you need to
look in /etc/profile.

If not, look in the /etc/X11/xdm/ tree for a broken script
or command in one of those files.

prompt# grep "a " *
               ^ is a SPACE

should give you some output.

Sounds like a "mis-typed alias" line or a line with an "a " 
(a space anything else) in it. [Make sense?]

Rick

On 31 Dec 1998, Kayvan Aghaiepour Sylvan wrote:

> Does anyone know what the plethora of these lines in my xdm-error.log are?
> 
>     bash: a: command not found
>     bash: a: command not found
>     bash: a: command not found
> 
> I'm using an entirely unmodified 5.2 XDM configuration.
> 
> A new line is added everytime a user logs into the machine using XDM.
> 
> 		      ---Kayvan
> -- 
> Kayvan Aghaiepour Sylvan |Sylvan Associates         | Proud Dad of:
> kayvan Sylvan COM        |http://www.isp.net/~kayvan| Katherine Yelena (8/8/89)
> (408) 978-1407 PGP OK    |Ask me about Avatar.      | Robin Gregory (2/28/92)
> 
> 
--
Rick L. Mantooth	rickdman cyberramp net
http://www.cyberramp.net/~rickdman
Lead me not into temptation, I can find it myself.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]