Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!think.com!spool.mu.edu!agate!tornado.Berkeley.EDU!et
From: et@tornado.Berkeley.EDU (Eric Thompson)
Newsgroups: comp.sys.att
Subject: serious problem w/tcsh binary (was: Re: Shells for SYSV machines)
Message-ID: <1991Jun17.202345.10281@agate.berkeley.edu>
Date: 17 Jun 91 20:23:45 GMT
References: <1991Jun10.170811.28341@ohsu.edu> <1526@gagme.chi.il.us> <JOHN.91Jun12111137@pitt.WPI.EDU>
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Organization: ucb
Lines: 32

[someone writes]:
>Instead of bash, I am now using tcsh, which i was able to ftp the
>binaries for from tesla.ee.cornell.edu, or (so I am told) from
>tut.cis.ohio-state.edu, or possibly cheops.cis.ohio-state.edu.  I
>forget which of the two sites is supposed to have it available.

I got the 3b2 tcsh binary from ee.cornell.edu, and it works fine,
EXCEPT that whenever I'm ROOT (on the console or su'd), it will
hang if I use a command string that includes a pipe to grep.  At
least, that's all that it's hung on so far.  It doesn't seem to
care which grep, either (grep,egrep,fgrep).

For example:

	# who /etc/wtmp | grep someuser
	# ps -ef | grep someprocess

The results will show up, but then when it should EXIT and return to
the prompt, it just hangs.  Using 'ps' from another terminal shows
just -tcsh running on the hung terminal.  The hung -tcsh is killable,
and this is the current solution.

Strangely, this doesn't happen if the user is NOT root.

Anyway, this isn't enough to keep me from using tcsh as the root shell,
but it makes me wonder if there are any other strange things lurking
in the binary that will break...

Help if you can!  :-)

thanks
Eric