yesĬhecking for SQLite3 library >= 3.0.0. yesĬhecking for _ZN7pcrecpp2RE4InitERKSsPKNS_10RE_OptionsE in -lpcrecpp. yesĬhecking for working ncursesw/curses.h. yesĬhecking for NcursesW wide-character library. ltinfoĬhecking for library containing Gpm_Open. none requiredĬhecking for library containing cur_term. ldlĬhecking for library containing backtrace. noĬhecking for library containing dlopen. lzĬhecking for library containing BZ2_bzopen. lutilĬhecking for library containing gzseek. yesĬhecking for library containing openpty. time.hĬhecking whether tzname is declared. bin/grepĬhecking whether struct tm is in sys/time.h or time.h. gcc -EĬhecking for grep that handles long lines and -e. yesĬhecking how to run the C preprocessor. none neededĬhecking whether gcc understands -c and -o together. yesĬhecking for gcc option to accept ISO C89. "pattern" : "^(?\\d/lib/python2.6/site-packagesĬhecking whether we are using the GNU C compiler. I suspect I just need to improve my understanding a bit further. If that wasn't enough the average log file size is ~80,000 lines!įortunately, it seems that lnav is well-suited to the task. The timeestamp is the 2nd column, the levels have nearly no meaning, and the messages are wildly different in their formatting and structure. The log format I want to point at lnav is unusual. I feel like I've got a handle on it now, but lnav isn't impressed with what I've done. I'm pretty solid with regex, but perl's spin on it took some reading. The potential of lnav is so vast, I could hardly believe my eyes when I stumbled upon it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |