That's not the best solution. Kent's suggestion was to put an echo in there to see what the script thought JAVA_HOME was, not to hardcode it.
The recommended location for environment variables is in your login environment, either system-wide or in your individual login environment. In other words, JAVA_HOME and CATALINA_HOME should be set for you (and the user Tomcat runs as) whether the Tomcat startup script is run or not. Otherwise, you will have to hardcode JAVA_HOME into every script in every Java-related software package you use, as any of them that expect to know where the JDK is will be looking for that variable. John > -----Original Message----- > From: Anup Ray [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, September 18, 2002 10:48 AM > To: Tomcat Users List; [EMAIL PROTECTED] > Subject: RE: Problem in tomcat installation in Solaris 8.0 > > > Thanks Kent. I traced out to a file setclasspath.sh and added > a line for > JAVA_HOME over there. This solved the startup problem. > Thanks again, > Anup > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
