From owner-freebsd-bugs Fri Jul 24 03:08:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA04924 for freebsd-bugs-outgoing; Fri, 24 Jul 1998 03:08:51 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA04919 for ; Fri, 24 Jul 1998 03:08:48 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA24202; Fri, 24 Jul 1998 20:08:22 +1000 Date: Fri, 24 Jul 1998 20:08:22 +1000 From: Bruce Evans Message-Id: <199807241008.UAA24202@godzilla.zeta.org.au> To: freebsd-bugs@FreeBSD.ORG, kargl@apl.washington.edu, rotel@indigo.ie Subject: Re: bin/7368: Added options to /usr/bin/time Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> How does one redirect via a shell the output of /usr/bin/time >> without redirecting the output from the command that is being >> timed. Using a real shell: time 3>&2 2>wherever sh -c "ls 2>&3 3>&-" ^^^^dup stderr on fd 3 ^^^^,^^^^ put back stderr, close fd 3 >> The answer is you can't, and is the motivation for the new >> options. Nope, see above. >time sh -c "ls >x 2>&1" >y 2>&1 Nope, this redirects the output of the command that is being timed. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message