On 9/7/20 2:13 PM, Dave Howorth wrote:
On Mon, 7 Sep 2020 13:53:18 -0700 Lew Wolfgang
wrote: On 9/7/20 12:49 PM, Doug McGarrett wrote:
If you look at the original post, it was lgrep, which didn't work. Then I ran grep -i etc. having looked up grep in "Linux in a Nutshell" my Linux reference book. But it turns out there actually is an lgrep in the system, and I installed it and ran it with the same result--nada. I didn't know about lgrep either. It's apparently a grep optimized for looking at logs. We're never to old to learn... What makes you think that?
According to https://manpages.debian.org/stretch/lv/lgrep.1 "lv also provides multilingual grep (1) functionality by giving it another name, lgrep"
https://github.com/olmeca/lgrep lgrep "A variation on grep, targeting log files" "lgrep is a variation on grep, developed specifically for efficient searching through application log files. Though most of the time an entry in a log file consists of one line, sometimes it spans multiple lines. A log entry usually consists of some metadata (e.g date, time, code reference) and a message. Sometimes the message part takes up multiple lines, e.g. if it contains a whole JSON object or a whole stack trace." Regards, Lew -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org