Re: Keeping tomcat up-to-date on linux
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave,
(Found this old message in my drafts folder. In case I didn't sent it,
here it is)
On 5/19/2010 11:55 PM, Dale Ogilvie wrote:
Yes, the release gap is an issue for me as well. Hence this email trail
:-)
Parallelism is achieved for us for other software by package updating
the test/dev server and testing that prior to performing the same
updates on prod. There is no need for us to have two versions of tomcat
running on the same host. So, if the package manager would just stay
up-to-date with tomcat releases it would mean we wouldn't have to have
special practices for Tomcat 6.
I'm pleased to hear that the upgrade process is trivial with your setup.
If you're going to have special practices, they might as well be simple.
On what did you base your init.d scripts? And what is your underlying
distro? We use redhat/fedora.
FWIW, we use the standard (Apache) distro of Tomcat on Debian Linux: no
apt-get or anything like that.
We have installed our own init.d script which is roughly this (we have
multiple applications running under separate TC instances):
#!/bin/sh
#
# Startup script for [our apps]
#
# chkconfig: 2345 99 01
# description: [our apps]
#
ANT=/usr/local/apache-ant-1.7.1/bin/ant
start() {
echo Starting [our apps] ...
su -c cd /path/to/TC/instance; ${ANT} tomcat-start tc-user
echo Done
}
stop() {
echo Stopping [our apps] ...
su -c cd /path/to/TC/instance; ${ANT} tomcat-stop tc-user
echo Done
}
restart() {
stop
sleep 5s
start
}
case $1 in
start)
start
;;
stop)
stop
;;
restart)
restart
;;
*)
echo Usage: $0 {start|stop|restart}
exit 1
esac
exit 0
Upgrading Tomcat does not require any changes to this script: instead,
we use Apache ant for everything, including choosing which TC base
install to use for the particular webapp. We generally use the same base
install (i.e. TC version) for all webapps, but they can be configured
independently as well.
If you have a simpler configuration than we do, you could also use a
symlink called apache-tomcat-current that points to the proper
directory and simply update the symlink when you upgrade TC.
If you're not already doing so, I /highly/ recommend the use of the
CATALINA_BASE environment variable to separate your webapp's
installation from the actual installation of Tomcat. It makes the
upgrade process of TC /super/ simple:
1. Download the latest version
2. Install/untar it somewhere distinct from the existing installations
3. Stop the existing Tomcat process
4. Change CATALINA_BASE to point to the new version
5. Start the Tomcat process
I couldn't be happier with this kind of setup.
- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkwOR1kACgkQ9CaO5/Lv0PAscACeKI3Quorfxl5poEz7/4K9R3w0
m4IAnA+ahteD5m3HNoZILbsz8gf81H/C
=IoDV
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Keeping tomcat up-to-date on linux
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dale, On 5/20/2010 6:40 PM, André Warnier wrote: Dale Ogilvie wrote: ... A free gift can vary greatly in it's final value, depending on it's actual usefulness and how many hidden costs it brings with it. I think that now you are *really* pushing it. People have been blacklisted from this list, and have had their Tomcat download license revoked for less than that. Please be sure that André is kidding about being blacklisted, etc. Since we're on proverbs, you might not want to bite the hand that feeds, though. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkv2sAwACgkQ9CaO5/Lv0PDg9QCgwjy9atK1mCk6Uiuz3O2neUiB D90Anj5WrMFdq+PYYfwad7tPz39rb/BH =sTxF -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Keeping tomcat up-to-date on linux
Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dale, On 5/20/2010 6:40 PM, André Warnier wrote: Dale Ogilvie wrote: ... A free gift can vary greatly in it's final value, depending on it's actual usefulness and how many hidden costs it brings with it. I think that now you are *really* pushing it. People have been blacklisted from this list, and have had their Tomcat download license revoked for less than that. Please be sure that André is kidding about being blacklisted, etc. I figured the tomcat download license made that pretty clear, but he.. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Keeping tomcat up-to-date on linux
I agree with Hassan, our reasons to use the tar.gz install method : * in most serious Tomcat environments you need more control over the installation and configuration than the distro managed version offers. * most distro's (especially RHEL) are lagging behind, so you don't get the latest stuff you need * we also keep an eye on this list and the tomcat website for updates, and for security patching we use some sort of subscription service from McAfee, so that should tell us if there are any security patches that need to be applied quickly. * it is usable and the same for all platforms we use * makes the separation of duty easier with our Linux administrators, at least I am sure I don't get unsolicited updates to my tomcat installations when they run an update on every package on every linux box * we run multiple Tomcat instances on the same OS image, that is not what the disto is facilitating * better open source support But the distro packaged version could be very usable for the masses and non-pro use. my two cents regards, Harry 2010/5/20 Dale Ogilvie dale.ogil...@trimble.co.nz Hi, The current release is 6.0.26, March 2010. RHEL5.x is running with Tomcat 5.5. Fedora 12 is on 6.0.20, June 2009 vintage. Ubuntu 10.04 is on 6.0.24 from Jan 2010. Ideally, the equivalent of a yum update would track tomcat releases so that soon after a tomcat release the tomcat6 package would move to the next minor release. Does this happen for any distro out there? What do people do to keep their tomcat patched up? Thanks Dale - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Keeping tomcat up-to-date on linux
navigation-case from-outcomeregister/from-outcome to-view-id/createUser.jsf/to-view-id redirect/ /navigation-case /navigation-rule navigation-rule from-view-id*/from-view-id navigation-case from-outcomeregistered/from-outcome to-view-id/confirmCreate.jsf/to-view-id redirect/ /navigation-case /navigation-rule navigation-rule from-view-id*/from-view-id /navigation-rule navigation-rule from-view-id/createUser.jsp/from-view-id navigation-case from-outcomeregistered/from-outcome to-view-id/confirmCreate.jsf/to-view-id /navigation-case /navigation-rule navigation-rule from-view-id*/from-view-id navigation-case from-outcomecommented/from-outcome to-view-id/commentSuccess.jsf/to-view-id /navigation-case /navigation-rule /faces-config Note the redirect tags... it works again but fails online -- From: Hassan Schroeder hassan.schroe...@gmail.com Sent: Thursday, May 20, 2010 7:00 AM To: Tomcat Users List users@tomcat.apache.org Subject: Re: Keeping tomcat up-to-date on linux On Wed, May 19, 2010 at 8:55 PM, Dale Ogilvie dale.ogil...@trimble.co.nz wrote: I'm pleased to hear that the upgrade process is trivial with your setup. If you're going to have special practices, they might as well be simple. Since I don't use package management for anything important, it's not special practice :-) On what did you base your init.d scripts? Don't remember, actually; I've been using pretty much the same basic version for a long time. I mean, it's just a shell script, eh? And what is your underlying distro? We use redhat/fedora. As a consultant, whatever the client's running; my own dev desktop system is SuSE, my own production server is RHEL, and I've got a couple of different Linux VMs on my MBP for testing. That changes periodically. And of course I'm running multiple Tomcats on the Mac too :-) Which, now that I think of it, is a good reason to install from the tar file; it's the same everywhere. I don't have to use yum here, rpm there -- the same simple drill works *everywhere*. Obviously, your situation sounds quite different from mine :-) -- Hassan Schroeder hassan.schroe...@gmail.com twitter: @hassan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Keeping tomcat up-to-date on linux
redirect/ /navigation-case navigation-case from-outcomeeditUser/from-outcome to-view-id/pages/user/EditUser.jsp/to-view-id /navigation-case /navigation-rule navigation-rule from-view-id*/from-view-id navigation-case from-outcometutorials/from-outcome to-view-id/pages/tutorials/tutorials.jsf/to-view-id redirect/ /navigation-case /navigation-rule navigation-rule from-view-id*/from-view-id navigation-case from-outcomeregister/from-outcome to-view-id/createUser.jsf/to-view-id redirect/ /navigation-case /navigation-rule navigation-rule from-view-id*/from-view-id navigation-case from-outcomeregistered/from-outcome to-view-id/confirmCreate.jsf/to-view-id redirect/ /navigation-case /navigation-rule navigation-rule from-view-id*/from-view-id /navigation-rule navigation-rule from-view-id/createUser.jsp/from-view-id navigation-case from-outcomeregistered/from-outcome to-view-id/confirmCreate.jsf/to-view-id /navigation-case /navigation-rule navigation-rule from-view-id*/from-view-id navigation-case from-outcomecommented/from-outcome to-view-id/commentSuccess.jsf/to-view-id /navigation-case /navigation-rule /faces-config Note the redirect tags... it works again but fails online -- From: Hassan Schroeder hassan.schroe...@gmail.com Sent: Thursday, May 20, 2010 7:00 AM To: Tomcat Users List users@tomcat.apache.org Subject: Re: Keeping tomcat up-to-date on linux On Wed, May 19, 2010 at 8:55 PM, Dale Ogilvie dale.ogil...@trimble.co.nz wrote: I'm pleased to hear that the upgrade process is trivial with your setup. If you're going to have special practices, they might as well be simple. Since I don't use package management for anything important, it's not special practice :-) On what did you base your init.d scripts? Don't remember, actually; I've been using pretty much the same basic version for a long time. I mean, it's just a shell script, eh? And what is your underlying distro? We use redhat/fedora. As a consultant, whatever the client's running; my own dev desktop system is SuSE, my own production server is RHEL, and I've got a couple of different Linux VMs on my MBP for testing. That changes periodically. And of course I'm running multiple Tomcats on the Mac too :-) Which, now that I think of it, is a good reason to install from the tar file; it's the same everywhere. I don't have to use yum here, rpm there -- the same simple drill works *everywhere*. Obviously, your situation sounds quite different from mine :-) -- Hassan Schroeder hassan.schroe...@gmail.com twitter: @hassan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Keeping tomcat up-to-date on linux
From: Pid * [mailto:p...@pidster.com] Subject: Re: Keeping tomcat up-to-date on linux Your problem isn't, at first glance, a Tomcat problem. Almost, if not all of your recent problems have been to do with JSF. You will be more likely to find the specific help you need elsewhere. Probably not, if the OP continues to call people idiots and hijack threads. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers.
Re: Keeping tomcat up-to-date on linux
On Thu, May 20, 2010 at 02:03:24PM +1200, Dale Ogilvie wrote: Hi, The current release is 6.0.26, March 2010. RHEL5.x is running with Tomcat 5.5. Fedora 12 is on 6.0.20, June 2009 vintage. Ubuntu 10.04 is on 6.0.24 from Jan 2010. Gentoo doesn't.have.versions.anymore is on 6.0.26 since around 30-Mar-2010. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Balance your desire for bells and whistles with the reality that only a little more than 2 percent of world population has broadband. -- Ledford and Tyler, _Google Analytics 2.0_ pgp3OyScLOssp.pgp Description: PGP signature
Re: Keeping tomcat up-to-date on linux
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hassan, On 5/19/2010 11:07 PM, Hassan Schroeder wrote: On Wed, May 19, 2010 at 7:39 PM, Dale Ogilvie dale.ogil...@trimble.co.nz wrote: I'm hoping for something a bit more distro managed. Presumably your method means you have to maintain your own init.d scripts and use the tar xzvf method of installation, outside of your distro package management system. I don't recall ever having to change anything but the paths in the init.d script, but yes, I do use `tar xvfz` to install. Which means I can install in parallel to any other running instance(s) and test before cutting over. The inability to do that with any package managers I'm aware of, plus the release gap, is why I don't bother with them. Untarring a file just doesn't seem all that onerous to me. Could the Tomcat download site(s) contain a well-known URL, like: http://www.apache.org/dist/tomcat/tomcat-6/apache-tomcat-current.tar.gz which redirects to the latest patch level for that version? That way, you could do something like this: $ wget 'http://www.apache.org/dist/tomcat/tomcat-6/apache-tomcat-current.tar.gz' [see what the name of the file is: if it's different than the last one installed, send an email to the administrator announcing that there's a new version ready to be installed] I'd never have a script auto-update a production machine for me, of course: I'd want to read the release notes, make sure that my configuration doesn't need any adjustments, etc. Of course, we don't put anything into production that hasn't been extensively tested in the first place, so it's not exactly a surprise when a new version needs to be installed. On Windows, I at least have an installer that takes care of these tasks for me. On Windows, I -- oh wait, I don't use Windows :-) Yeah, same here: I can't imagine running a production system on Windows. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkv1qskACgkQ9CaO5/Lv0PDPXwCeN2+MWnqjHEtkzz9/QkDrLKXJ KsIAn28b2Km3Er+Z9gQCsMTr4TR4pogk =k59c -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Keeping tomcat up-to-date on linux
* We are serious about our tomcat install, and find configuration file and jvm tweaks about all we need to do. * Agreed that most distro's (apart from the rolling release ones such as gentoo, arch) are lagging behind. This is the problem in my view. * I would rather delegate the responsibility for security patches to the distro, like I do for kernel security patches. * I want security and feature updates to the other software on the distro, hence they are not unsolicited. Because these updates occur on the test/dev system first, after passing distro QA, it seems pretty unlikely a problem will effect our tomcat install on PROD. Distros are all about delegation of *maintenance* responsibility to the distro from the end-user. This frees up the end-user to actually build apps, not the app-server. Current distros seem to be not interested in maintaining tomcat packages at the minor version release level. Pity. But then again, responses seem to be that the .tar.gz package is good enough for the community. Perhaps that is my answer. Thanks! Dale -Original Message- From: Harry Metske [mailto:harry.met...@gmail.com] Sent: Thursday, 20 May 2010 6:33 p.m. To: Tomcat Users List Subject: Re: Keeping tomcat up-to-date on linux I agree with Hassan, our reasons to use the tar.gz install method : * in most serious Tomcat environments you need more control over the installation and configuration than the distro managed version offers. * most distro's (especially RHEL) are lagging behind, so you don't get the latest stuff you need * we also keep an eye on this list and the tomcat website for updates, and for security patching we use some sort of subscription service from McAfee, so that should tell us if there are any security patches that need to be applied quickly. * it is usable and the same for all platforms we use * makes the separation of duty easier with our Linux administrators, at least I am sure I don't get unsolicited updates to my tomcat installations when they run an update on every package on every linux box * we run multiple Tomcat instances on the same OS image, that is not what the disto is facilitating * better open source support But the distro packaged version could be very usable for the masses and non-pro use. my two cents regards, Harry - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Keeping tomcat up-to-date on linux
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave,
On 5/19/2010 11:55 PM, Dale Ogilvie wrote:
Yes, the release gap is an issue for me as well. Hence this email trail
:-)
Parallelism is achieved for us for other software by package updating
the test/dev server and testing that prior to performing the same
updates on prod. There is no need for us to have two versions of tomcat
running on the same host. So, if the package manager would just stay
up-to-date with tomcat releases it would mean we wouldn't have to have
special practices for Tomcat 6.
I'm pleased to hear that the upgrade process is trivial with your setup.
If you're going to have special practices, they might as well be simple.
On what did you base your init.d scripts? And what is your underlying
distro? We use redhat/fedora.
FWIW, we use the standard (Apache) distro of Tomcat on Debian Linux: no
apt-get or anything like that.
We have installed our own init.d script which is roughly this (we have
multiple applications running under separate TC instances):
#!/bin/sh
#
# Startup script for [our apps]
#
# chkconfig: 2345 99 01
# description: [our apps]
#
ANT=/usr/local/apache-ant-1.7.1/bin/ant
start() {
echo Starting [our apps] ...
su -c cd /path/to/TC/instance; ${ANT} tomcat-start tc-user
echo Done
}
stop() {
echo Stopping [our apps] ...
su -c cd /path/to/TC/instance; ${ANT} tomcat-stop tc-user
echo Done
}
restart() {
stop
sleep 5s
start
}
case $1 in
start)
start
;;
stop)
stop
;;
restart)
restart
;;
*)
echo Usage: $0 {start|stop|restart}
exit 1
esac
exit 0
Upgrading Tomcat does not require any changes to this script: instead,
we use Apache ant for everything, including choosing which TC base
install to use for the particular webapp. We generally use the same base
install (i.e. TC version) for all webapps, but they can be configured
independently as well.
If you have a simpler configuration than we do, you could also use a
symlink called apache-tomcat-current that points to the proper
directory and simply update the symlink when you upgrade TC.
If you're not already doing so, I /highly/ recommend the use of the
CATALINA_BASE environment variable to separate your webapp's
installation from the actual installation of Tomcat. It makes the
upgrade process of TC /super/ simple:
1. Download the latest version
2. Install/untar it somewhere distinct from the existing installations
3. Stop the existing Tomcat process
4. Change CATALINA_BASE to point to the new version
5. Start the Tomcat process
I couldn't be happier with this kind of setup.
- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkv1sHcACgkQ9CaO5/Lv0PATmACbByuxe3maW7iV27X8zy35XFJW
J2AAnj7z3OFnsCyj/UTAAa+XFa+4XytE
=Gwn2
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Keeping tomcat up-to-date on linux
Hi. I think in all of this, you may be overlooking one element : the distributions you seem to be talking about are free, and made by volunteers who donate their time. That includes Tomcat. There are other distributions which are not free, where the people making them actually get paid for doing so, and for testing them together with other packages, and for handling a whole concept of global releases. For those you pay, and you are then entitled to complain (to them) if they lag behind, or do not provide the tools you would wish for. It is your choice to subscribe to one or the other. As often mentioned on this forum also, contributions are always welcome. In my country, there is a proverb : if you receive a horse (as a present, for free), then you should not check his teeth. My apologies if I misinterpreted your post below. Dale Ogilvie wrote: * We are serious about our tomcat install, and find configuration file and jvm tweaks about all we need to do. * Agreed that most distro's (apart from the rolling release ones such as gentoo, arch) are lagging behind. This is the problem in my view. * I would rather delegate the responsibility for security patches to the distro, like I do for kernel security patches. * I want security and feature updates to the other software on the distro, hence they are not unsolicited. Because these updates occur on the test/dev system first, after passing distro QA, it seems pretty unlikely a problem will effect our tomcat install on PROD. Distros are all about delegation of *maintenance* responsibility to the distro from the end-user. This frees up the end-user to actually build apps, not the app-server. Current distros seem to be not interested in maintaining tomcat packages at the minor version release level. Pity. But then again, responses seem to be that the .tar.gz package is good enough for the community. Perhaps that is my answer. Thanks! Dale -Original Message- From: Harry Metske [mailto:harry.met...@gmail.com] Sent: Thursday, 20 May 2010 6:33 p.m. To: Tomcat Users List Subject: Re: Keeping tomcat up-to-date on linux I agree with Hassan, our reasons to use the tar.gz install method : * in most serious Tomcat environments you need more control over the installation and configuration than the distro managed version offers. * most distro's (especially RHEL) are lagging behind, so you don't get the latest stuff you need * we also keep an eye on this list and the tomcat website for updates, and for security patching we use some sort of subscription service from McAfee, so that should tell us if there are any security patches that need to be applied quickly. * it is usable and the same for all platforms we use * makes the separation of duty easier with our Linux administrators, at least I am sure I don't get unsolicited updates to my tomcat installations when they run an update on every package on every linux box * we run multiple Tomcat instances on the same OS image, that is not what the disto is facilitating * better open source support But the distro packaged version could be very usable for the masses and non-pro use. my two cents regards, Harry - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Keeping tomcat up-to-date on linux
From: André Warnier [mailto:a...@ice-sa.com] Subject: Re: Keeping tomcat up-to-date on linux In my country, there is a proverb : if you receive a horse (as a present, for free), then you should not check his teeth. Slightly different in English-based cultures: Don't look a gift horse in the mouth. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Keeping tomcat up-to-date on linux
My intent is purely to find the best solution for an up-to-date tomcat on linux. If we have to pay for an up-to-date tomcat on linux we will. Indeed we would prefer to roll up the cost for up-to-date tomcat in our current commercial distro fees. From responses it seems: 1. that there is no up-to-date tomcat package on non-free linux. 2. that .tar.gz is the only up-to-date option on linux generally. 3. that .tar.gz is considered a workable option. I smile at the gift horse in mouth statements. A free gift can vary greatly in it's final value, depending on it's actual usefulness and how many hidden costs it brings with it. -Original Message- From: André Warnier [mailto:a...@ice-sa.com] Sent: Friday, 21 May 2010 10:05 a.m. To: Tomcat Users List Subject: Re: Keeping tomcat up-to-date on linux Hi. I think in all of this, you may be overlooking one element : the distributions you seem to be talking about are free, and made by volunteers who donate their time. That includes Tomcat. There are other distributions which are not free, where the people making them actually get paid for doing so, and for testing them together with other packages, and for handling a whole concept of global releases. For those you pay, and you are then entitled to complain (to them) if they lag behind, or do not provide the tools you would wish for. It is your choice to subscribe to one or the other. As often mentioned on this forum also, contributions are always welcome. In my country, there is a proverb : if you receive a horse (as a present, for free), then you should not check his teeth. My apologies if I misinterpreted your post below. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Keeping tomcat up-to-date on linux
Dale Ogilvie wrote: ... A free gift can vary greatly in it's final value, depending on it's actual usefulness and how many hidden costs it brings with it. I think that now you are *really* pushing it. People have been blacklisted from this list, and have had their Tomcat download license revoked for less than that. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Keeping tomcat up-to-date on linux
Hi, The current release is 6.0.26, March 2010. RHEL5.x is running with Tomcat 5.5. Fedora 12 is on 6.0.20, June 2009 vintage. Ubuntu 10.04 is on 6.0.24 from Jan 2010. Ideally, the equivalent of a yum update would track tomcat releases so that soon after a tomcat release the tomcat6 package would move to the next minor release. Does this happen for any distro out there? What do people do to keep their tomcat patched up? Thanks Dale - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Keeping tomcat up-to-date on linux
On Wed, May 19, 2010 at 7:03 PM, Dale Ogilvie dale.ogil...@trimble.co.nz wrote: What do people do to keep their tomcat patched up? I watch this list for announcements of new releases and install them :-) Of course, reading the release notes lets me decide how urgently that needs to happen and/or how much testing I want to do before going to production with a new version. FWIW, -- Hassan Schroeder hassan.schroe...@gmail.com twitter: @hassan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Keeping tomcat up-to-date on linux
Hassan Schroeder wrote: I watch this list for announcements of new releases and install them :-) I'm hoping for something a bit more distro managed. Presumably your method means you have to maintain your own init.d scripts and use the tar xzvf method of installation, outside of your distro package management system. On Windows, I at least have an installer that takes care of these tasks for me. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Keeping tomcat up-to-date on linux
On Wed, May 19, 2010 at 7:39 PM, Dale Ogilvie dale.ogil...@trimble.co.nz wrote: I'm hoping for something a bit more distro managed. Presumably your method means you have to maintain your own init.d scripts and use the tar xzvf method of installation, outside of your distro package management system. I don't recall ever having to change anything but the paths in the init.d script, but yes, I do use `tar xvfz` to install. Which means I can install in parallel to any other running instance(s) and test before cutting over. The inability to do that with any package managers I'm aware of, plus the release gap, is why I don't bother with them. Untarring a file just doesn't seem all that onerous to me. On Windows, I at least have an installer that takes care of these tasks for me. On Windows, I -- oh wait, I don't use Windows :-) -- Hassan Schroeder hassan.schroe...@gmail.com twitter: @hassan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Keeping tomcat up-to-date on linux
Yes, the release gap is an issue for me as well. Hence this email trail :-) Parallelism is achieved for us for other software by package updating the test/dev server and testing that prior to performing the same updates on prod. There is no need for us to have two versions of tomcat running on the same host. So, if the package manager would just stay up-to-date with tomcat releases it would mean we wouldn't have to have special practices for Tomcat 6. I'm pleased to hear that the upgrade process is trivial with your setup. If you're going to have special practices, they might as well be simple. On what did you base your init.d scripts? And what is your underlying distro? We use redhat/fedora. Dale - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Keeping tomcat up-to-date on linux
On Wed, May 19, 2010 at 8:55 PM, Dale Ogilvie dale.ogil...@trimble.co.nz wrote: I'm pleased to hear that the upgrade process is trivial with your setup. If you're going to have special practices, they might as well be simple. Since I don't use package management for anything important, it's not special practice :-) On what did you base your init.d scripts? Don't remember, actually; I've been using pretty much the same basic version for a long time. I mean, it's just a shell script, eh? And what is your underlying distro? We use redhat/fedora. As a consultant, whatever the client's running; my own dev desktop system is SuSE, my own production server is RHEL, and I've got a couple of different Linux VMs on my MBP for testing. That changes periodically. And of course I'm running multiple Tomcats on the Mac too :-) Which, now that I think of it, is a good reason to install from the tar file; it's the same everywhere. I don't have to use yum here, rpm there -- the same simple drill works *everywhere*. Obviously, your situation sounds quite different from mine :-) -- Hassan Schroeder hassan.schroe...@gmail.com twitter: @hassan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Keeping tomcat up-to-date on linux
Exactly right, Hassan. I think it is extremely unwise to leave any critical portion of one's system--personal, development, or production--at the hands of the distro. I've used Linux for over a decade, and install Apache, Java, Tomcat, etc. by hand. ALWAYS. Oft times I build Apache myself. On Wed, May 19, 2010 at 10:25 PM, Hassan Schroeder hassan.schroe...@gmail.com wrote: On Wed, May 19, 2010 at 7:03 PM, Dale Ogilvie dale.ogil...@trimble.co.nz wrote: What do people do to keep their tomcat patched up? I watch this list for announcements of new releases and install them :-) Of course, reading the release notes lets me decide how urgently that needs to happen and/or how much testing I want to do before going to production with a new version. FWIW, -- Hell hath no limits, nor is circumscrib'd In one self-place; but where we are is hell, And where hell is, there must we ever be --Christopher Marlowe, 'Doctor Faustus' (v, 121-24)
