Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!spool.mu.edu!uwm.edu!www.nntp.primenet.com!nntp.primenet.com!news.mathworks.com!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: cat foo* > foo.bar causes infinite loop Date: 17 Nov 1996 09:12:12 GMT Organization: Private BSD site, Dresden Lines: 19 Message-ID: <56mktc$b4a@uriah.heep.sax.de> References: <328A1236.32C4@pilot.msu.edu> <56itkk$h59$1@nic.wat.hookup.net> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E schaffer@wat.hookup.net wrote: > You should expect this behavior with any shell (no, I haven't tried): > basically, the shell first looks for pipes, redirections etc. For > redirected stdout it creates the target file, then evaluates the command > (cat foo*). Just for the records, all of the available shells for FreeBSD (csh, tcsh, sh, bash, zsh) experience this behaviour, except the pdksh. (I haven't tried to get a genuine ksh, but somebody else already responded that it doesn't show this artifact.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)