Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 83783 invoked from network); 3 Jan 2002 01:40:46 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 3 Jan 2002 01:40:46 -0000 Received: (qmail 2300 invoked by uid 97); 3 Jan 2002 01:40:31 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 2281 invoked by uid 97); 3 Jan 2002 01:40:30 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 2270 invoked from network); 3 Jan 2002 01:40:30 -0000 Sender: cj Message-ID: <3C33B485.DD3ED621@goldencode.com> Date: Wed, 02 Jan 2002 20:31:49 -0500 From: Cynthia Jeness Organization: Golden Code Development Corp X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Tomcat Users List , dwlee1@ameritech.net Subject: Re: TomCat RPM's Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Donald, The rpm builds two files in /usr/bin -- tomcat4 and tomcatd. To start or stop Tomcat, just use tomcat4 start or tomcat4 stop. One other issue with the RPM is that it su's to the tomcat4 user, but the var/tomcat4 directory is owned by root. The tomcat4 user needs at least write access to the logs directory. Finally, the default port is 8180 and not 8080 with the rpm. Other than that, the rpm worked fine. Based on my experience, I put together my own documentation -- some of this is specific to our AJUG (Atlanta Java User Group) site. If you are interested, check out: http://www.ajug.org/howto/tomcat4.html Cindy Jeness Donald Lee wrote: > I went to > http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.1/rpms/ > downloaded tomcat4-4.0.1-1.noarch.rpm > installed using rpm -iv tomcat4-4.0.1-1.noarch.rpm > everything appeared to be going ok until I came to the part in the doc > file I found called running.txt > > "execute shell command: > $CATALINA_HOME/bin/startup.sh" > > That didn't work. > It turns out my Tomcat installation went to > /var/tomcat4 > which is where I set $CATALINA_HOME to. > I looked in the $CATALINA_HOME/bin directory and to my surprise, there > was no startup.sh, only a bootstrap.jar. I searched my whole system > for a startup.sh and could not find one, so I decided that something > was dreadfully wrong, and went back to the tomcat site. > I went into > http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.1/bin/ > this time and downloaded jakarta-tomcat-4.0.1.zip > I unpacked it and it created it's own directory of > jakarta-tomcat-4.0.1. I basically cut and pasted the contents of that > directory into my /var/tomcat4 directory and over wrote all > directories and files. I then ran $CATALINA_HOME/bin/startup.sh and > tested my installation with http://localhost:8080 and all appears to > be well.I have a question, when I installed the rpm it created a > directory etc/tomcat4/conf/tomcat4.conf. As this was not part of my > list of installation procedures, can I assume that this directory/file > is not needed? I was wondering if I could safely delete this > directory or is something left out of the running.txt file? > Can anybody tell me what the purpose of the rpms are if they do not > properly install tomcat? > > Thanks, and God Bless and have a happy new year! > > -- > To unsubscribe: > For additional commands: > Troubles with the list: -- To unsubscribe: For additional commands: Troubles with the list: