From owner-freebsd-current  Mon Apr  3 07:08:21 1995
Return-Path: current-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA07429 for current-outgoing; Mon, 3 Apr 1995 07:08:21 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA07423 for <current@freebsd.org>; Mon, 3 Apr 1995 07:08:04 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id AAA25922 for current@freebsd.org; Tue, 4 Apr 1995 00:04:46 +1000
Date: Tue, 4 Apr 1995 00:04:46 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199504031404.AAA25922@godzilla.zeta.org.au>
To: current@FreeBSD.org
Subject: time(1) exit status for killed processes
Sender: current-owner@FreeBSD.org
Precedence: bulk

time(1) exits with status (st >> 8) when the process being timed exits
with status `st'.  This causes it to exit with status 0 when the process
is killed by a signal.

Is this bug traditional?  I noticed it because a process that executed
`time foo' assumed that input from the file written by `foo' didn't need
to be validated, and copied nonexistent input to stdout forever.

Bruce