Not a bad link, but I have to comment on the guys suggestion about changing the catalina.sh script. Here's a quote:
"In my many years of consulting, I have learned not to rely on environment variables which can be unset by ignorant or malicious people" In my many years of consulting, I've much more often encountered problems with people tampering with script files that should have been left alone. Ever do an export JAVA_HOME= to explicitly pick a JVM and be stumped by a bug still happening . . . only to find out that someone took at upon themselves to change a script that you know well, and to manually set JAVA_HOME withing that script? This much more sinister than missing environment variables. If you're very afraid of environment variables not being there or being wrong, then make a script file that sets a few variables and then calls the original script. Or some variant of that. But just jumping in and altering the script is rarely the best idea. - T.B. --- "Cocalea, Eugen" <[EMAIL PROTECTED]> wrote: > Heh, seem that people around here knock on the same problems I had few days > ago. Best solution, found on: > > http://www.ubeans.com/tomcat/ __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
