If TYPE is without-match, when grep discovers null input binary data it assumes that the rest of the file does not match this is equivalent to the -I option. I don't understand what I am doing wrong with my first grep command. When some output is suppressed, grep follows any output with a one-line message saying that a binary file matches. But in the file /var/log/auth.log the "Apr 12" entries are present as we can see if I run this command (I also proved it by printing the whole file with cat): > less /var/log/auth.log | grep -c "Apr 12" So if I try the following command: > less /var/log/auth.log | grep "Apr 12" port 40466 ssh2Īs we can see, there are only entries until the Apr 11th. port 40684 ssh2Īpr 11 20:48:06 sshd: Accepted password for root from. port 40735 ssh2Īpr 11 19:58:44 sshd: Accepted password for root from. port 40808 ssh2Īpr 11 18:13:46 sshd: Accepted password for root from. port 40765 ssh2Īpr 11 18:12:30 sshd: Accepted password for root from. port 62535 ssh2Īpr 11 18:12:12 sshd: Accepted password for root from. (the file handling bit) (c) 2005, Joel Schopp (the ugly bit) (c) 2007,2008, Andy Whitcroft (new conditions, test suite. port 48686 ssh2Īpr 10 12:09:03 sshd: Accepted password for root from. port 48990 ssh2Īpr 10 10:11:17 sshd: Accepted password for root from. port 49061 ssh2Īpr 10 09:42:38 sshd: Accepted password for root from. It can’t display the contents of binary files, but it can search inside them and tell you if something matches. But it seems like grep isn't processing the whole file, instead grep is stopping at some point: > less /var/log/auth.log | grep AcceptedĪpr 10 08:32:43 sshd: Accepted password for root from. The grep command calls such proprietary file types binary files. I'm trying to print all root accesing attempts from /var/log/auth.log with grep.
0 kommentar(er)
