Re: tail -f and pipes with bash shell

2005-05-19 Thread Lev Bishop
On 19/05/05, Igor Pechtchanski wrote: > On Thu, 19 May 2005, Dave Korn wrote: > > Amusingly enough, those were still both legitimate email addresses even > > after he X'd them out! oops. > That's why one ought to X out the top-level suffix too. I don't believe > .XXX is a valid suffix. Or

RE: tail -f and pipes with bash shell

2005-05-19 Thread Igor Pechtchanski
On Thu, 19 May 2005, Dave Korn wrote: > Original Message > >From: Lev Bishop > >Sent: 12 May 2005 23:56 > > > On 12/05/05, Lev Bishop wrote: > >> On 11/05/05, Peter Ekberg wrote: > > > > Sorry, sorry, sorry. > > > > 'kin

RE: tail -f and pipes with bash shell

2005-05-19 Thread Dave Korn
Original Message >From: Lev Bishop >Sent: 12 May 2005 23:56 > On 12/05/05, Lev Bishop wrote: >> On 11/05/05, Peter Ekberg wrote: > > Sorry, sorry, sorry. > > 'kin gmail. > > Lev Amusingly enough, those were still bo

RE: tail -f and pipes with bash shell

2005-05-12 Thread Peter Ekberg
Lev Bishop wrote: > Try "grep --line-buffered" to get grep to flush output after every > line. There is a performance penalty for doing this. I don't know why > you don't see the buffering when grep's stdout isn't redirected. > Perhaps grep (or the std library) removes/reduces buffering in the > ca

Re: tail -f and pipes with bash shell

2005-05-12 Thread Lev Bishop
Try "grep --line-buffered" to get grep to flush output after every line. There is a performance penalty for doing this. I don't know why you don't see the buffering when grep's stdout isn't redirected. Perhaps grep (or the std library) removes/reduces buffering in the case the output is a terminal.

RE: tail -f and pipes with bash shell

2005-05-12 Thread Peter Ekberg
Lev Bishop wrote: > On 11/05/05, Peter Ekberg wrote: >> What is going on here? > > My guess: "tail frame.log" closes its stdout as soon as it has read > the requested lines from the file, "tail -f frame.log" keeps its > stdout open, since it is waiting for new lines to be added to the > logfile. C

Re: tail -f and pipes with bash shell

2005-05-12 Thread Lev Bishop
On 12/05/05, Lev Bishop <[EMAIL PROTECTED]> wrote: > On 11/05/05, Peter Ekberg <[EMAIL PROTECTED]> wrote: Sorry, sorry, sorry. 'kin gmail. Lev -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports:

Re: tail -f and pipes with bash shell

2005-05-12 Thread Lev Bishop
On 11/05/05, Peter Ekberg <[EMAIL PROTECTED]> wrote: > What is going on here? My guess: "tail frame.log" closes its stdout as soon as it has read the requested lines from the file, "tail -f frame.log" keeps its stdout open, since it is waiting for new lines to be added to the logfile. Cat is using

tail -f and pipes with bash shell

2005-05-11 Thread Peter Ekberg
Hello! What is going on here? ~$ ps -f | grep $$ peda2316 1 con 20:21:51 /usr/bin/bash peda31802316 con 21:51:47 /usr/bin/ps peda31642316 con 21:51:47 /usr/bin/grep [I use bash, if that matters] ~$ tail -f frame.log | grep Antenna 2005-05-11,21:51:07: