DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12089>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12089 CATALINA_HOME ignored and reset by catalina.sh Summary: CATALINA_HOME ignored and reset by catalina.sh Product: Tomcat 4 Version: 4.1.9 Platform: All OS/Version: All Status: NEW Severity: Major Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] catalina.sh header documentation claims you can set CATALINA_HOME but actually catalina.sh will ignore (reset) whatever you specify and jam the value to the location of catalina.sh. This was not always true -- Revision 1.20 (from 4.0.1) actually let you set this and it wouldn't step on the value. You can fix this by adding back in the logic: if [ -z "$CATALINA_HOME" ] ; then around the setting of it. Or, (IMO a worse alternative), if you really don't want to provide this hook into the script, then document that CATALINA_ROOT is no longer an environment variable of interest -- and document that the actual location of catalina.sh must be identical to CATALINA_ROOT. (I don't like this because I use symbolic links to break out the various components of CATALINA_ROOT and I don't want catalina.sh assuming that everything is physically in the same directory.) Also, depending on how you resolve this problem, it is imperative that you resolve http://nagoya.apache.org/bugzilla/showvotes.cgi?bug_id=12065 By the way, the addition of CATALINA_BASE is a good step in the right direction. In additional nice step would be to separate CATALINA_BASE_CONFIG (for instance configuration files -- ie, readonly files) from CATALINA_BASE_OUTPUT (for instance log, work, and temp files, ie, writeable files) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
