You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by GOMEZ Henri <hg...@slib.fr> on 2000/05/22 12:40:33 UTC
tomcat 3.1 final patches
Hi,
Could someone provide a patch file for tomcat 3.1 final which
contain bugs correctives.
Not all users 3.1 could run pre 3.2 release (especially night builds).
Many thanks ;-)
-
Henri Gomez ___[_]____
EMAIL : gomez@slib.fr (. .)
PGP KEY : 4912D659 ...oOOo..(_)..oOOo...
PGP Fingerprint : 8CAD0D50356DA7E45C540B010FFE39E8
Re: tomcat 3.1 final patches
Posted by Jeff Hoffman <je...@headland-media.com>.
One of the things that it seems like I've noticed is that we had a server
that was used for development purposes that had 3.1 of Tomcat installed. A
week or so later we downloaded 3.1 again from the site when we were
installing it on the production servers, and it was a slightly different
build or something because things on the development server wouldn't work on
production. Several of us went over the configuration files and whatnot and
couldn't find a problem. Finally, we copied over the /lib directory and
still didn't have any luck with it. A day or two later, I copied both the
lib and bin directories off the development server over to the production
machine and suddenly the things that weren't working started working.
I really feel the tomcat team should consider release numbering similar to
linux kernels where they have a <major>.<minor>.<release> versioning number
rather than just <major>.<minor>. Then they could have nightly builds and
fixes that are more clearly demarked so that people don't have the problems
that I had.
Also, I have a few other suggestions if anyone is interested (If not, just
stop reading here)
I was unable to find a way to get Tomcat to tell me what version it is with
a command line option like -v.
It would be nice to have Tomcat able to run as a non-root user when started
as root similar to apache, especially considering it's a webserver like
apache when running stand alone, at least then it could bind to port 80 and
not be a huge security hole. (have there been any exploits to the Tomcat
product in stand alone or other mode?)
It would be nice to see the option functional to bind to a specific IP
address when it's run (the option is there but currently only port mapping
seems to work).
At any rate, it's a great product so far and I see a lot of good changes on
the way. Keep up the good work Tomcat Team! It's appreciated.
-jeff hoffman
headland digital media : webmaster
513 755 0086
----- Original Message -----
From: "GOMEZ Henri" <hg...@slib.fr>
To: <to...@jakarta.apache.org>
Sent: Monday, May 22, 2000 6:43 AM
Subject: tomcat 3.1 final patches
> Hi,
>
> Could someone provide a patch file for tomcat 3.1 final which
> contain bugs correctives.
>
> Not all users 3.1 could run pre 3.2 release (especially night builds).
>
> Many thanks ;-)
>
> -
> Henri Gomez ___[_]____
> EMAIL : gomez@slib.fr (. .)
> PGP KEY : 4912D659 ...oOOo..(_)..oOOo...
> PGP Fingerprint : 8CAD0D50356DA7E45C540B010FFE39E8
>
> --------------------------------------------------------------------------
> To unsubscribe, email: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commmands, email: tomcat-user-help@jakarta.apache.org
>