Currently I am using
tail -f for viewing logs.
Is there any more efficient/readable/better way of viewing logs?
closed as not constructive by Ƭᴇcʜιᴇ007, BinaryMisfit, Dave, Diogo, 8088 Jan 11 '13 at 17:54
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.
Instead of using
For viewing/browsing logs,
Depending on what you're awaiting for... you may have to build a little script for matching exactly your need.
You may found some useable samples in perlfaq, like in
I've already used this many times for triggering special cases.
For sample, there is a
Would produce one line, self-refreashing every seconds, containing all seen daemon's name and a counter for each of them:
As F. Hauri suggests, you could use perl to format the output.
For my usage, I created an alias for tail in my
In my case, I toggled visual bell on, so my screen blinks on error (and my speaker doesn't beep) and error/warning lines can be detected very quickly.
You can get more information about:
Again, as F. Hauri explains in his answer, you can do many things thanks to perl, so you could "develop" your own log reader depending on your needs.