Urm, this is probably better suited to the tomcat-dev list.  Replies
intermixed.

"Hans Schmid" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi,
>
> I just tried the newest version of tomcat.sh in the 3.3.1 version of TC
> Works like a charme (I need the JDPA support which I hardcoded before)
>
> One small comment (subject for discussion):
>
> I think it would make sense to change
>
> # Read local properties
> if [ -f $HOME/.tomcatrc ] ; then
>   . $HOME/.tomcatrc
> fi
>
> to
>
> # Read local properties
> if [ -f ../.tomcatrc ] ; then
>   . ../.tomcatrc
> fi
>
> Note the .. instead the $HOME

I don't particularly like it, since it depends on where the script is
lauched from.  What I, personally, do in my init.d scripts is something
like:
  HOME=/path/to/this/tomcat/home $TOMCAT_INSTALL/bin/startup.sh

>
> My setup:
> I have 4 different Tomcats installed which use all the same Tomcat
> installation in in
> TOMCAT_HOME (/usr/tomcat).

I admit that the scripts could be better about setting tomcat.install.  This
would also work around problems with Mac/Classic (that are hopefully fixed
in 3.3.2-dev).

>
> BTW. I have 4 tomcat directories with 4 bin and conf dirs set up for this.
> Is there a simpler way of distinguishing the different profiles?
>

Having separate $TOMCAT_HOME directories is in some ways the easiest way to
go.  I don't generally don't go this way, and instead use the '-f
<config-file>' option to specify different Tomcats running on the same box.

>
> All 4 Tomcats need different memory settings -Xms and -Xmx
> Currently $HOME/.tomcatrc points to a single profile configuration
> With my change every tomcat gets its own configuration .tomcatrc file
> instead of a single global one.
>
> If we decide to leave it as it is, we might consider to change the $HOME
to
> $TOMCAT_HOME for consistency.
>
> What do you think?
>
> Regards,
> Hans
>
> Hans Schmid
>
> einsurance Agency AG
> Information Technology
> Bayerstrasse 33
> 80335 M�nchen
>
> Tel: +49-89-55292-860
> Fax: +49-89-55292-855




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to