I'm answering my own post to correct an error in what I wrote.
On Saturday 15 March 2003 20:06, shlomo solomon wrote:
> And, as I already wrote, although I can't explain it, the buffer problem
> disappeared. I know it makes no sense, but the first couple of times I ran
It turns out that my testin
This thread is interesting, but if people are still trying to help with my
original question, let me just repeat that using tee does solve the problem.
And since there's been alot of theorizing about C programs and making changes
to buffer routines in existing programs, let me just say that (for
On Sat, Mar 15, 2003, Shaul Karl wrote about "Re: pipe question":
> Am I right that you could have done it in C (as well as with other
> languages) by duplicating the file descriptors, redirecting some of them
> and so on? The reason for asking is that bash has some of these
On 2003-03-13, shlomo solomon <[EMAIL PROTECTED]>:
> I have a script that puts a lot of output on the screen. I want to look for a
> particular string in the output, so I pipe the output to GREP. That works
> fine, but here's the problem. I also want to see the output on the terminal,
> and the pi
On Fri, Mar 14, 2003, shlomo solomon wrote about "Re: pipe question":
> So what's my problem? It seems that both the above solutions are writing to a
> buffer and the actual screen output is not immediate, but in spurts. Let me
> make that clearer. The original script cre
On 2003-03-13, shlomo solomon wrote:
> I have a script that puts a lot of output on the screen. I want to look for a
> particular string in the output, so I pipe the output to GREP. That works
> fine, but here's the problem. I also want to see the output on the terminal,
> and the pipe to GREP mea
On Friday 14 March 2003 12:20, Yedidyah Bar-David wrote:
> On Fri, Mar 14, 2003 at 01:23:23AM +0200, Tzafrir Cohen wrote:
> > On Thu, Mar 13, 2003 at 11:11:13PM +0200, shlomo solomon wrote:
> > > Hi,
> >
> > I also recall a "multi-cat" or "multi-pipe" file, but can't seem to find
> > it anywhere.
>
On Fri, 14 Mar 2003 09:35:55 +0200
shlomo solomon <[EMAIL PROTECTED]> wrote:
> So what's my problem? It seems that both the above solutions are writing to a
> buffer and the actual screen output is not immediate, but in spurts.
That's a result of stdio default behaviour. Each application can
cont
On Fri, Mar 14, 2003 at 09:35:55AM +0200, shlomo solomon wrote:
>
> So what's my problem? It seems that both the above solutions are writing to a
> buffer and the actual screen output is not immediate, but in spurts. Let me
> make that clearer. The original script creates a few hundred lines of
On Fri, Mar 14, 2003 at 01:23:23AM +0200, Tzafrir Cohen wrote:
> On Thu, Mar 13, 2003 at 11:11:13PM +0200, shlomo solomon wrote:
> > Hi,
> >
>
> I also recall a "multi-cat" or "multi-pipe" file, but can't seem to find
> it anywhere.
multitee
Didi
==
First, thanks to all who answered. I now have a partial solution to my
problem.
On Friday 14 March 2003 02:23, Omer Zak wrote:
> If Shlomo uses X-Window, then he can have his script write its stuff to a
> file.
> Then in another window, he can run:
> tail -f script-output-file
> and in a third
If Shlomo uses X-Window, then he can have his script write its stuff to a
file.
Then in another window, he can run:
tail -f script-output-file
and in a third window, he can run:
tail -f script-output-file | grep whatever\.\*pattern
--- Omer
My opinio
On Fri, Mar 14, 2003, Tzafrir Cohen wrote about "Re: pipe question":
> tee to a file
>..
> I also recall a "multi-cat" or "multi-pipe" file, but can't seem to find
> it anywhere.
>
> Also: can this be done using a more complicated redirectio
On Thu, Mar 13, 2003 at 11:11:13PM +0200, shlomo solomon wrote:
> Hi,
>
> I spent a couple of hours looking for this, but I bet one of the bash gurus
> can help me here ;-).
>
> I have a script that puts a lot of output on the screen. I want to look for a
> particular string in the output, so I
>Hi,
>
>I spent a couple of hours looking for this, but I bet one of the bash
gurus
>can help me here ;-).
>
>I have a script that puts a lot of output on the screen. I want to look
for a
>particular string in the output, so I pipe the output to GREP. That
works
>fine, but here's the problem. I
On Thursday 13 March 2003 23:11, shlomo solomon wrote:
> Hi,
>
> I have a script that puts a lot of output on the screen. I want to look for
> a particular string in the output, so I pipe the output to GREP. That works
> fine, but here's the problem. I also want to see the output on the
> terminal,
Hi,
I spent a couple of hours looking for this, but I bet one of the bash gurus
can help me here ;-).
I have a script that puts a lot of output on the screen. I want to look for a
particular string in the output, so I pipe the output to GREP. That works
fine, but here's the problem. I also wan
17 matches
Mail list logo
