I'm working with a Windows-10 computer, using a WSL.
I'm investigating a logfile, produced by
NLog in a C# application. I'm expecting log entries to appear everywhere throughout the file, but I see the following:
Linux prompt> grep "geen mengcontainer" logfile.log 2023-03-07 07:25:08.7971 | Warn | ... | geen mengcontainer. 2023-03-07 07:25:09.8285 | Warn | ... | geen mengcontainer. 2023-03-07 07:25:10.8754 | Warn | ... | geen mengcontainer. Binary file logfile.log matches
As you see, after 07:25:10, the
grep stops, even though the file goes further for the rest of the day. There seems to be some character, telling
grep that the file is not a textfile, but a binary file, causing
grep to stop working.
Some more information about the file:
Linux prompt>file logfile.log logfile.log: ASCII text, with CRLF line terminators
Some more information about my Linux WSL installation:
Linux prompt>uname -a Linux ComputerName 4.4.0-19041-Microsoft #2311-Microsoft Tue Nov 08 17:09:00 PST 2022 x86_64 x86_64 x86_64 GNU/Linux Linux prompt> cat /etc/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" ... VERSION_CODENAME=focal UBUNTU_CODENAME=focal
Some more information about my
Linux prompt> grep --version grep (GNU grep) 3.4
What can I do?
- Does anybody know how to find and replace the character, which is responsible for
grepto stop filtering?
- Does anybody know which extra parameter or switch I can add to
grepin order not to stop filtering?
- Does anybody know about a
grepversion which does not behave like this? (Please take into account that
apt updatethings don't work on my environment)
Thanks in advance