From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27360 invoked from network); 29 Jan 1997 13:05:43 -0000 Received: from euclid.skiles.gatech.edu (list@130.207.146.50) by coral.primenet.com.au with SMTP; 29 Jan 1997 13:05:43 -0000 Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id HAA19910; Wed, 29 Jan 1997 07:52:43 -0500 (EST) Resent-Date: Wed, 29 Jan 1997 07:52:43 -0500 (EST) Date: Wed, 29 Jan 1997 14:52:35 +0200 (EET) Message-Id: <199701291252.OAA27397@bacchus.math.jyu.fi> From: Risto J Laitinen To: zsh-workers@math.gatech.edu Subject: Re: Zsh reporting bad return status of commands In-Reply-To: <25218.199701281713@stone.dcs.warwick.ac.uk> References: <19970128085622.NH31021@@> <25218.199701281713@stone.dcs.warwick.ac.uk> Reply-To: rjl@math.jyu.fi Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Resent-Message-ID: <"Hv_CA1.0.1t4.RWqxo"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/2840 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu zefram@dcs.warwick.ac.uk writes: > Clint Olsen wrote: > >Interesting. Then it must be broken on SunOS since it is also set there > >but it doesn't print out the bad exit status. > ... > >pdxgp1 ~# ls /foo > >/foo not found > > No, it's just that the native ls on SunOS (and Solaris) returns an exit > code of 0 under these circumstances. A bug in ls? It wouldn't be the > first one. It's just the BSD variant of ls that returns 0: kanto% uname -a SunOS kanto 5.4 Generic_101945-41 sun4m sparc kanto% /usr/bin/ls /foo; echo $? /foo: No such file or directory 2 kanto% /usr/ucb/ls /foo; echo $? /foo not found 0