- To: SLUG <slug@xxxxxxxxxxx>
- Subject: Re: [SLUG] tailing, following and filtering
- From: Penedo <penedo@xxxxxxxxx>
- Date: Thu, 23 Nov 2006 13:30:50 +1100
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=rKkX0nG44mLz3eF7ENfjLlXicjSqmyT0nBU4/b8drTMeX7HBq7OOVRIJXTCukIfBPy6y/NdLKqH0gOO9u0kt3CbIY/h6mTb5bLC+7y3eLE5ZSvezCZlo+HyE17ewEgy7vYUxvM6wTNNOEU8wUAxZDD9dJbqXZoldDmxNufrK8kM=
On 23/11/06, Matthew Hannigan <mlh@xxxxxxxxxx> wrote:
On Thu, Nov 23, 2006 at 08:23:37AM +1100, Penedo wrote:
> On 23/11/06, Howard Lowndes <lannet@xxxxxxxxxxxxx> wrote:
> >I want to tail -f the syslog file but I only want to see what I want to
> >see and I don't want to see what I don't what to see. The idea is to
> >tail follow through a filter. Is that possible.
>
> What's wrong with "tail -f syslog | grep ..."?
Buffering
Can you elaborate? It works for me (I mean - I get the output through
grep as soon as tail wakes up and reads the line).
--P
SLUG Mailing List Archives