4 ms·
Interesting! Do you know how it compares to multitail? (https://www.vanheusden.com/multitail/ https://www.vanheusden.com/multitail/) They look very similar.
by clumsysmurf 4y ago
Interesting! Do you know how it compares to multitail? (https://www.vanheusden.com/multitail/ https://www.vanheusden.com/multitail/) They look very similar.
- tstack 4y agoI don't think multitail really understands logs like lnav does, it's just following the last lines in the file. For example, if you try to follow multiple files in multitail like so: $ multitail /var/log/install.log -I /var/log/system.log You get a view with the tail from one file followed by the tail from the other, they are not collated by timestamp. In contrast, if you do the same thing in lnav: $ lnav /var/log/install.log /var/log/system.log You will get a single view with all of the log messages from both files and they're sorted by their timestamps. Here is all of what lnav is doing: * Monitoring files/directories for updates * Decompressed files/archives * Detected the log format for each file * Created SQLite vtables that provide access to log messages * Built an index of all the log messages in all the files so you can jump to a certain point in time or to the next/previous error message. * Display all log messages with syntax highlighting
- aargh_aargh 4y agoI migrated from multitail to lnav. Turned out to be a no-brainer. I second the above, just one pain point with multitail to add. I often page/search/filter in the scrollback buffer (I typoed "bugger" - Freudian slip?) and in multitail the scrollback is a separate window with a frame and everything, which is a pain (copying whole lines using mouse includes the frame, ugh). The filtering/searching being a separate pain. One thing I used in multitail and not sure if I migrated wholly to lnav was log file syntax highlighting using regexes.