Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 2790 invoked from network); 20 Mar 2011 11:04:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 Mar 2011 11:04:17 -0000 Received: (qmail 86265 invoked by uid 500); 20 Mar 2011 11:04:13 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 86105 invoked by uid 500); 20 Mar 2011 11:04:13 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 86096 invoked by uid 99); 20 Mar 2011 11:04:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Mar 2011 11:04:13 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of aw@ice-sa.com designates 212.85.38.228 as permitted sender) Received: from [212.85.38.228] (HELO tor.combios.es) (212.85.38.228) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Mar 2011 11:04:04 +0000 Received: from [192.168.245.129] (p549E0599.dip0.t-ipconnect.de [84.158.5.153]) by tor.combios.es (Postfix) with ESMTPA id 23F9622611D for ; Sun, 20 Mar 2011 12:03:43 +0100 (CET) Message-ID: <4D85DF00.5070501@ice-sa.com> Date: Sun, 20 Mar 2011 12:03:28 +0100 From: =?ISO-8859-1?Q?Andr=E9_Warnier?= Reply-To: Tomcat Users List User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Installing Tomcat the Brute Force Way? References: <768FEA3F936926468F594E3CA7741FE8018B983A@ipa-vault.nvipa.com> <99C8B2929B39C24493377AC7A121E21FACD8A7704E@USEA-EXCH8.na.uis.unisys.com> <768FEA3F936926468F594E3CA7741FE802C742B3@ipa-vault.nvipa.com> <99C8B2929B39C24493377AC7A121E21FACD8A77050@USEA-EXCH8.na.uis.unisys.com> <768FEA3F936926468F594E3CA7741FE802C742B4@ipa-vault.nvipa.com> <99C8B2929B39C24493377AC7A121E21FACD8A77052@USEA-EXCH8.na.uis.unisys.com> <768FEA3F936926468F594E3CA7741FE802C742CE@ipa-vault.nvipa.com> In-Reply-To: <768FEA3F936926468F594E3CA7741FE802C742CE@ipa-vault.nvipa.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Robinson, Eric wrote: >>> From looking at the server, it would appear that tomcat was >> installed >>> using tomcat-6.0.18-0.noarch.rpm. >> Now you're in trouble. The 3rd-party repackaged versions of >> Tomcat typically scatter files all over, and then try to get >> things back together with symlinks. You're better off doing >> a proper install on the new server. Had you used a real >> Tomcat, life would be much easier. >> >> - Chuck >> > > Not necessarily. I did an rpm -qlp on tomcat-6.0.18-0.noarch.rpm. All > the files it installs are in /opt/tomcat > The files, yes. But it is highly likely that it installs also links from /etc/tomcat, /usr/share/tomcat, /usr/lib/tomcat, /var/lib/tomcat and so on. At least, that is what most Linux packages that I know are doing. To take a top-down view, you generally have two major choices : A) you download and install the "real tomcat" from tomcat.apache.org. That one installs everything below one top directory. It is easy to install, copy, update, etc.. * on its own *. If your purpose is mainly Tomcat-centric (e.g. you want to test Tomcat or develop for Tomcat, you have only this one server where you need to take care of it etc..), then that is probably the easiest solution. It is also easier to get support on this list, because with that one, everyone knows where to look for the files. And, that is also the right one to use of you want the very latest version available. OR B) you go with whatever package manager system is used by the target server, and use whatever "best" version they've got. As Chuck says, these packages have a tendency to spread files and links all over, if you look at it from a purely Tomcat point of view. But if you have to manage a bunch of servers, and Tomcat is only one little part in what you have to manage, and/or you need Tomcat to interact with other software packages which need to be of compatible versions etc.., then packages are definitely easier. I personally find it rather sweet to be able, on a new Debian Linux system fresh out of the box : - apt-get install sun-jdk6 - apt-get install apache2 - apt-get installl tomcat6 - apt-get install apache2-mod-jk (more or less) and have it all just work, and have it all put its startup scripts where (as a sysadmin) you expect (/etc/init.d), its logfiles where you expect them (/var/log/apache2 and /var/log/tomcat6) (and they get rotated too), its configuration files where you expect them (/etc/apache2 and /etc/tomcat6), and so on. It gets a little bit more puzzling when it comes time to figure out where (or if) it has installed the demo webapps though, or where exactly to find Tomcat's startup.sh, and whether the system is using it or not.. But you have a choice, and that's the nice part. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org