Thank you KOM I will take a look at using ee or clog it seems like that will allow me to do the searches I need.
I'm thinking "time" might not be the best way to express the log file limits because that will change depending on the amount of traffic. 1 day of traffic for you might be 2 or 3 days for someone else or vice versa. I have the email reports package and I had it send me what it had which should be a full day but not in this case because I reset the logs yesterday evening. The email size will be larger than the actual file because it also includes an RRD image of the traffic but probably not by too much. The email is 16megs, spans "Mar 10 20:39:32" to "Mar 11 14:10:55" and is almost exactly 100,000 lines (that's one line per entry at 160 bytes per entry). That's just over 17 hours or approximately (less than) 1 meg per hour. At that rate I should be able to get somewhere around 700 hours of logging or almost a month which will do nicely now that I know how to search it. :) Obviously, on a busy or slow month that could change considerably.
Anyway, I just included all that stuff to help anyone that comes along later that wants to try calculating things. Lots of rounding and estimating going on so try to use your own numbers if you can.
Note, I saved all the lines into a text file and that's only 15.7 megs.
Thanks for your help everyone.
Joe