Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!uwm.edu!bionet!ames!dftsrv!cdc910b21.gsfc.nasa.gov!lait
From: lait@cdc910b21.gsfc.nasa.gov (Leslie Lait)
Newsgroups: comp.sys.sgi
Subject: Re: tcsh problems on Personal IRIS...
Message-ID: <2849@dftsrv.gsfc.nasa.gov>
Date: 19 Jul 90 21:13:26 GMT
References: <9007180038.aa28638@VMB.BRL.MIL>
Sender: news@dftsrv.gsfc.nasa.gov
Reply-To: lait@cdc910b21.gsfc.nasa.gov.UUCP (Leslie Lait)
Organization: NASA Goddard Space Flight Center, Greenbelt MD
Lines: 35


In article <9007180038.aa28638@VMB.BRL.MIL> Claude.P.Cantin@NRC.CA writes:
>
>I have downloaded the tcsh binaries from the archive site, and installed
>it on a 4D/240S, 4D/260S, 4D/280S, and a Personal IRIS.
>
> ...
>
>   2. Loging in as a user, the same thing happens, AND I can't start
>      a wsh at all!!!  In other words, it's useless!!!!
>
>If I go back to the password file and change the login shell back to
>/bin/csh, everything is back to normal....
>

We had the same problem on our PI running 3.2:
 o  tcsh worked fine when invoked from an existing wsh window.
 o  No wsh windows could be created if tcsh was set as the default shell.
 o  Logins from a terminal (not the console) worked fine.

When we had problems, wsh was complaining (in the SYSLOG file) that it 
could not find the command tcsh. (We had the binary in /usr/local/bin/)

The command
   ln -s /usr/local/bin/tcsh /bin/tcsh
seemed to solve the problem.  (/usr/local/bin/ is on a different
disk with a lot more free space, which is one reason why we did not
simply move the binary to /bin/ ) 

Hope this helps.

Leslie Robert Lait                 | If you put a billion monkeys in front of a
lait@cdc910b21.gsfc.nasa.gov       | billion typewriters typing at random, they
                                   | would reproduce the entire collected
My opinions are my own, not NASA's.| works of UseNet in about...five minutes.