Bug 36922 - setup.sh file mis-advertised and missing
Summary: setup.sh file mis-advertised and missing
Status: RESOLVED FIXED
Alias: None
Product: Tomcat 5
Classification: Unclassified
Component: Catalina (show other bugs)
Version: 5.5.9
Hardware: Other Linux
: P3 enhancement (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL: http://jakarta.apache.org/tomcat/tomc...
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-04 23:49 UTC by Don Koch
Modified: 2010-10-04 18:22 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Don Koch 2005-10-04 23:49:50 UTC
On the above web page, the documentation states:

The file $CATALINA_HOME/bin/jsvc/native/tomcat.sh can be used as a template for
starting Tomcat automatically at boot time from /etc/init.d. The file is
currently setup for running Tomcat 4.1.x, so it is necessary to edit it and
change the classname from BootstrapService to Bootstrap.

First off, $CATALINA_HOME/bin/jsvc is a file, not a directory.  Nowhere in
$CATALINA_HOME, does a tomcat.sh file exist; it isn't in the tar file.
Comment 1 Yoav Shapira 2005-11-10 19:52:38 UTC
I see a tomcat.sh in the jsvc.tar.gz file: it's under the native subdirectory,
as the instructions suggest.  And if you copy the files created when making jsvc
under a directory with that name, jsvc is a directory in addition to a file.
Comment 2 Don Koch 2005-11-12 01:08:47 UTC
(In reply to comment #1)
> I see a tomcat.sh in the jsvc.tar.gz file: it's under the native subdirectory,
> as the instructions suggest.  And if you copy the files created when making jsvc
> under a directory with that name, jsvc is a directory in addition to a file.

It can't be both in the same place.

The web page is *STILL* wrong.  It's the next to the last paragraph.
Comment 3 Yoav Shapira 2005-11-18 16:44:07 UTC
It CAN be in two places: first it's in the tar.gz file, then it's wherever you
expand the tar.gz file.

But let's try this: please provide the text you'd like to see on the setup
documentation page.  I'll be glad to apply any clarifications or further
explanations on the documentation that make you happy.
Comment 4 Mark Thomas 2006-10-07 13:56:07 UTC
The docs make sense to me but I am also sure they could be improved. To
re-iterate Yoav's comments, if you would like to provide some alternative words
we would be happy to consider them.

Marking as an ehancement.
Comment 5 Mark Thomas 2010-10-04 18:22:04 UTC
This page was updated when the commons-daemon packaging was updated.