Path: utzoo!mnetor!uunet!mcvax!botter!ark!maart
From: maart@cs.vu.nl (Maarten Litmaath)
Newsgroups: comp.unix.questions
Subject: Re: Weird things in csh (and kernel?)
Message-ID: <1195@ark.cs.vu.nl>
Date: 25 Feb 88 21:18:33 GMT
References: <1193@ark.cs.vu.nl> <662@sjoerd.cs.vu.nl>
Reply-To: maart@cs.vu.nl (Maarten Litmaath)
Organization: VU Informatica, Amsterdam
Lines: 27
Keywords: csh, script

In article <662@sjoerd.cs.vu.nl> sjoerd@cs.vu.nl (Sjoerd Mullender) writes:
\In article <1193@ark.cs.vu.nl> maart@cs.vu.nl (Maarten Litmaath) writes:
\>	% a.out < a.out
\>	a.out: Text file busy.
\>	%
\If you are debugging a.out then this could happen.  Especially if you have set
\breakpoints.

I was NOT debugging a.out...

\>...
\>	% ./echo > echo
\>...
\When executing the command "./echo > echo" the shell will first create the
\file echo.  It then tries to exec ./echo.  The kernel refuses (it's not an
\object anymore, it an empty file) and the shell will start interpreting the
\script.  The shell will fork off a new shell to do the work.  This new shell
\will first execute ~/.cshrc which contains the command "echo echo hello".

Isn't it a BOURNE shell that is forked off, which won't execute ~/.cshrc?

\Why was this cross-posted to comp.unix.wizards?

Possible kernel bugs are detected by wizards only, I guess.
-- 
"Brothers & sisters, praise the Lord, |Maarten Litmaath @ Free U Amsterdam:
send your money, Rolls Royce > Ford." |maart@cs.vu.nl, mcvax!botter!ark!maart