@morantis: Do you not find it strange that a uncompressed log file with 12 million entries is 97KB in size? Ask anyone programmer and they'll tell you it's impossible. Even if each entry was only a single character as opposed to a full log line, you'd be looking at an 11MB file size.
If you don't find that strange and want to find out why that's up to you. If you do want to prove to yourself, then as mentioned, check for the IP suggested, run "ls -lh" in the log dir and run "wc -l" and "wc -c" on each of the log files.
No need to paste the results on here, since I have my doubts over whether you're honestly just misunderstanding something, or simply trolling, but on the off chance you're being honest, give them a go and prove it to yourself. As you say, you've nothing to prove to us, but perhaps you should prove it to yourself.
I ran the above on a log file of mine, 60027 entries (for a period of 30 days), which would suggest a 4MB file size if an average log entry was 70 characters. Run all the commands suggested and you get, 60027 entries, 6061146 characters, 5.8MB in size. An expected and realistic size.
Now, I could be pulling these numbers out of thin air, but anyone on this forum who has access to a mac or linux machine or a router that provides "ls -lh", "wc -l" and "wc -c" will be able to reproduce the exact same results by running those commands on any uncompressed log file. The number of characters reported will be an exact match for the file size reported (when converted from bytes to KB or MB). The number of entries * estimated characters per line, will give you a rough but still in the right ball park file size.
I doubt however, anyone will be able to come up with an uncompressed log file that contains 12 million entries and has a 97KB file size. Keep taking the blue pill if you wish though.
Last edited by JoeD; 05-22-2012 at 07:31 AM.
|