Re: bash vs. ksh

2006-05-10 Thread Michael Erdely
Philip Guenther wrote: No, that command does exactly what the sentence before it describes it as doing. Just because you _usually_ want the "2>&1" after the ">" doesn't mean you _always_ do. Philip Guenther You're absolutely right. I didn't read the above paragraph. -ME -- Support OpenBSD:

Re: bash vs. ksh

2006-05-10 Thread Philip Guenther
On 5/10/06, Michael Erdely <[EMAIL PROTECTED]> wrote: ... I was going to respond with the exact same thing. Then, just for kicks, I decided to read ksh(1) from 3.9 and searched for "2>". I found: "$ cat /foo/bar 2>&1 > /dev/null | cat -n" Here's a patch: ... No, that command does exactly wha

Re: bash vs. ksh

2006-05-10 Thread Ray Lai
On Wed, May 10, 2006 at 04:35:46PM -0400, Michael Erdely wrote: > Janjaap van Velthooven wrote: > >>Luke Bakken wrote: > cmd1 2>&1 >$WHERE > >What you would want is > >cmd1 >$WHERE 2>&1 > > I was going to respond with the exact same thing. Then, just for kicks, > I decided to read ksh(1) fr

Re: bash vs. ksh

2006-05-10 Thread tdonahue
> Luke Bakken wrote: >>> cmd1 2>&1 >$WHERE >> >> This doesn't do what you think it does, which I'm assuming is redirect >> stderr and stdout to $WHERE. >> > > What does it do? I was of the belief that it is indeed doing the above, > and the log/scratch files I redirect to have always seemed to bac

Re: bash vs. ksh

2006-05-10 Thread Michael Erdely
Janjaap van Velthooven wrote: Luke Bakken wrote: cmd1 2>&1 >$WHERE What you would want is cmd1 >$WHERE 2>&1 I was going to respond with the exact same thing. Then, just for kicks, I decided to read ksh(1) from 3.9 and searched for "2>". I found: "$ cat /foo/bar 2>&1 > /dev/null | cat -n"

Re: bash vs. ksh

2006-05-10 Thread Janjaap van Velthooven
On Wed, May 10, 2006 at 01:17:21PM -0500, Mark Rolen wrote: > Luke Bakken wrote: > >> cmd1 2>&1 >$WHERE > > > > This doesn't do what you think it does, which I'm assuming is redirect > > stderr and stdout to $WHERE. > > What does it do? I was of the belief that it is indeed doing the above, Par

Re: bash vs. ksh

2006-05-10 Thread Adam
On Wed, 10 May 2006 13:17:21 -0500 Mark Rolen <[EMAIL PROTECTED]> wrote: > Luke Bakken wrote: > >> cmd1 2>&1 >$WHERE > > > > This doesn't do what you think it does, which I'm assuming is redirect > > stderr and stdout to $WHERE. > > > > What does it do? I was of the belief that it is indeed do

Re: bash vs. ksh

2006-05-10 Thread Spruell, Darren-Perot
From: [EMAIL PROTECTED] > Luke Bakken wrote: > >> cmd1 2>&1 >$WHERE > > > > This doesn't do what you think it does, which I'm assuming > is redirect > > stderr and stdout to $WHERE. > > > > What does it do? I was of the belief that it is indeed doing > the above, > and the log/scratch files

Re: bash vs. ksh

2006-05-10 Thread Mark Rolen
Luke Bakken wrote: >> cmd1 2>&1 >$WHERE > > This doesn't do what you think it does, which I'm assuming is redirect > stderr and stdout to $WHERE. > What does it do? I was of the belief that it is indeed doing the above, and the log/scratch files I redirect to have always seemed to back that up,

Re: bash vs. ksh

2006-05-10 Thread Luke Bakken
cmd1 2>&1 >$WHERE This doesn't do what you think it does, which I'm assuming is redirect stderr and stdout to $WHERE.