Access log too large to open?

[hondafox400]

I've neglected checking/wiping my access log in Apache for quite some time now, and now it is 110MB large (D'oh!). I tried opening it with Notepad, but it just froze up and went unresponsive. Should I just stop Apache, delete the 110MB file, and create a new "access.txt" in the logs folder? Is the access long named access.txt, or access.log or something?

[danieljean]

ouch!

Now I know why it's common to split up log files per day, e.g. localhost_access_log.2004-01-17.txt; I suggest you set that up asap.

As for the old file, everything is not lost. A bit of scripting should be able to split that up in more manageable units, perl or php would likely be ideal. Alternately, another program may be able to open it.

[papamaku]

how do you do the log splitting, i.e. whats the config command?

as i have the same problem

thanks

[Brett_Tabke]

> 110MB

LOL! (WebmasterWorld for the week is dozens of gigs). I load it right up in EditPlus. no problemo.

Use a file splitter to split the file up.

[Sinner_G]

You should be able to import that document into a database such as MS Access or even into Excel.

[papamaku]

Use a file splitter to split the file up

Which would you recommend? For Apache2, to put the logs into access_ddmmyy.log format?