On Sunday 29 March 2009 22:25:55 Charles Howse wrote: > On Mar 29, 2009, at 1:54 PM, Glen Barber wrote: > > On Sun, Mar 29, 2009 at 1:33 PM, Charles Howse <cho...@charter.net> > > > > wrote: > >> On Mar 28, 2009, at 11:51 PM, Olivier Nicole wrote: > >>> Hi, > >>> > >>>> Webalizer is doing what it's supposed to with httpd-access.log, but > >>>> when I give it the error log to process is coughs, spits and spills > >>>> out errors with no data processed. My research hasn't turned up a > >>>> good solution for webalizer and -error.log. > > > > What are the errors? > > Intrusion attempts, (a few) bad links in my website, also I use the > error.log to troubleshoot cgi scripts.
Nothing beats tail -f for debugging. 404's can be gathered from access log, by webalizer (or awstats or ...) and are summarized when enabled. If I remember correctly, there's also a referer top list, that specifies which pages link to invalid pages, but it may have been awstats that does this. Can't think of anything specific for apache error log, I roll my own grok rules if I'm really interested in a specific vulnerability. See sysutils/grok. -- Mel _______________________________________________ email@example.com mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"