|
Reading this debate day in and day out has be thinking about writing a damn tail program. There's no question that it could be done. Perhaps a first pass would be a message queue monitor that updates automatically and dynamically adjusts filtering to the user's specifications. Next step, a DB monitor? -----Original Message----- From: James Rich [mailto:james@eaerich.com] Sent: Wednesday, November 20, 2002 5:43 PM To: midrange-l@midrange.com Subject: RE: Question Re: Piping and Redirection 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 _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.