On Thu, 2002-11-07 at 15:47, Mark Eggers wrote: > RPMs are evil, RPMs are evil . . .
There definitely are some painful things about the Tomcat rpms, but once you understand their quirks they are fine. Here are their quirks that I know of so far: Tomcat LE doesn't install when using JDK 1.4. You have to install Tomcat full, even though it shouldn't be necessary (I think). /etc/tomcat4/tomcat4.conf defines the default user as tomcat4. If you are running it on port 80, this needs to be set to root. This is more of a bug/misfeature in Linux than a Tomcat problem, but it is a quirk. You MUST have a /etc/java/java.conf file to set JAVA_HOME. I think that the startup scripts could be smarter and use `which java` to find JAVA_HOME based on the location of JAVA_HOME/bin/java, but they don't so make sure that /etc/java/java.conf exists. I have not found any way to get JNI stuff to work at all with the rpms, short of installing the relevant jars in JAVA_HOME/jre/lib/ext (I think that's the path). tomcat4.conf suggests that I can put an export LD_LIBRARY_PATH in it and that will work but it doesn't. The only two ways to get JMagick to work are to put it in jre/lib/ext or to edit dtomcat4 so that it is in the classpath. This isn't right. But, after getting those problems fixed, the rpms are very handy. Maybe there should be a "How do I use the RPMs" faq? -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
