I think Edix's answer is the most pragmatic. Also, someone at work actually crashed a service by opening the log files in vim. I think the problem was that the

I think Edix's answer is the most pragmatic. Also, someone at work actually crashed a service by opening the log files in vim. I think the problem was that the memory and processor were already getting stomped on (thus the need to look at the logs) and vim tried to do a lot of fancy stuffs to get more info on the file as a whole.