Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!wuarchive!psuvax1!rutgers!cbmvax!grr
From: grr@cbmvax.commodore.com (George Robbins)
Newsgroups: comp.unix.ultrix
Subject: Re: Does your /usr/bin/csh grow and die under Ultrix 3.1C?
Message-ID: <14435@cbmvax.commodore.com>
Date: 14 Sep 90 05:52:35 GMT
References: <9009131437.AA17137@watcgl.waterloo.edu>
Reply-To: grr@cbmvax.commodore.com (George Robbins)
Organization: Commodore, West Chester, PA
Lines: 19

In article <9009131437.AA17137@watcgl.waterloo.edu> root@watcgl.uwaterloo.ca (Ian! D. Allen [CGL]) writes:
> Every now and then someone's csh loops, eats all the memory on the machine,
> and dies.  This most often happens when logging in, when the .cshrc/.login
> is being processed.  Anyone else seen this?  DS5400, Ultrix 3.1C.

The csh distributed with 3.1C is more or less what used to be /usr/new/csh,
but with some bugs added that evoke the behavoir that you describe.  There
are patches available for 3.1C that replace this csh with a more traditional
one, which you should install.

If you've already received the 4.0 distribution, but haven't installed it
yet, another alternative is to extract the 4.0 csh, which seems to work
just fine under 3.1C...  Likewise you can install one from one of the older
risc ultrix/uws releases if you don't care about command recall, etc.

-- 
George Robbins - now working for,     uucp:   {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing:   domain: grr@cbmvax.commodore.com
Commodore, Engineering Department     phone:  215-431-9349 (only by moonlite)