RE: Question Re: Piping and Redirection -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: RE: Question Re: Piping and Redirection
From: James Rich <james@xxxxxxxxxxx>
Date: Wed, 20 Nov 2002 15:43:17 -0700 (MST)
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On Thu, 21 Nov 2002, Evan Harris wrote:

> I'm still mystified as to why you would want to watch the log files. Seems
> to me that constantly watching them would be more disruptive than getting a
> break message  - especially when you can't easily filter the log by a
> severity level. Or can you ?

When using tail to monitor files (log files or any other file) you can
filter what you want by piping with grep:

tail -f /my/file | grep "string to watch for"

James Rich

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.