If you’re like me, you’ve had to support Apache Tomcat for a good chunk of your IT career, and it hasn’t all been wine and roses. Typically Tomcat will work great in a development, or in a proof of concept environment, but when it comes time to put it in production and have it face some real traffic, well, you get complaints. Now, why do I have a picture of Tomcat on a messenger bag here? It’s because I would like to put Tomcat in a bag…and throw it in a river! But, since I haven’t done that (yet), I’ll talk about recently when I had some tomcat servers pumping out hundred of MGs of logfiles that weren’t being rotated quickly enough, filling up the log partition and causing alerts to go off. Now logrotate is supposed to handle things, and while it’s defaults will generally work fine, any persistant error from tomcat will make the logs quickly eat up all your space and cause you grief, so it’s best to set it up to handle them ahead of time. First take a look at:
Recent Comments
- m2m news on LinkedIn is spamming all of my Gmail contacts
- LDN Games on HOWTO build your own open source Dropbox clone
- Rinkesh on Aquadots sweetened with the date-rape drug 1,4-butanediol
- Lars on HOWTO retrieve email with fetchmail and forward it on with procmail
- fak3r » HOWTO automate Debian installs with preseed | Linux Blog on HOWTO automate Debian installs with preseed
Tags
apache apple art bands barack obama bash bsd code debian dubya eff election email features gamer google hacker health howto lighttpd linux mp3 music networking newstudy obama open source phishing politics president rock rock and roll security spam tech terror tv ubuntu unix varnish video games vote web webserver wii


At the 











Home