I wouldn't delete "work" itself...that will probably break things.
My scripts just have:
rm -rf /usr/local/tomcat/work/*
on stop. That way, a startup is clean. Tomcat will rebuild anything it needs to build under "work". That will slow things down the first time through, however, as the cache is rebuilt. If you have to stop/start Tomcat often, there's probably something else wrong that should be investigated and resolved.
John
On Wed, 02 Apr 2003 15:02:51 -0500, Erik Price <[EMAIL PROTECTED]> wrote:
John Turner wrote:
I don't think Tomcat clears out the work directory on its own. I've always had to write wrapper scripts for my instances that do a "rm -rf work/*" right before a call to startup.sh.
Oh okay, I didn't realize that's how it's supposed to work. No problem. I also just noticed that the contents of the work directory are owned by root, and I'm just a user on my friend's Linux server. I'll just let him know that if ever feels that the directory is getting too big he can clean it out, or modify startup.sh to do so.
Is it safe to assume that anything in $CATALINA_HOME/work will be rebuilt by Tomcat (assuming the webapp starts normally and the "current" JSPs are still present in the webapp's docroot)? It's less trouble for him if he just has to delete one directory ($CATALINA_HOME/work) instead of doing a separate delete for every webapp.
Thanks,
Erik
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
