You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Rainer Frey <ra...@inxmail.de> on 2010/07/12 10:31:27 UTC
setenv.sh and CATALINA_BASE
Hi,
in the default case (just one instance, supplied start scripts), CATALINA_BASE
is set to CATALINA_HOME. But this assignment,
if [ -z "$CATALINA_BASE" ] ; then
CATALINA_BASE="$CATALINA_HOME"
fi
is done *after* reading setenv.sh. Is this for a specific reason, or just
accidently?
The reason why I ask is: I want to put some custom config files (specifically:
jmxremote access and password files) in the conf directory, and setup system
properties with the path to these files in setenv.sh., but I can't use
$CATALINA_BASE/conf unconditinally because it is not set at that point by the
default scripts.
(I don't want to use $CATALINA_HOME/conf uncontitionally either, as I'll use
this setenv.sh also in a multi-instance setup).
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: setenv.sh and CATALINA_BASE
Posted by Rainer Frey <ra...@inxmail.de>.
On Thursday 15 July 2010 20:26:14 Christopher Schultz wrote:
> Rainer,
Hi, and sorry for the late reply.
[I changed the order of some parts of your mail to reply
> On 7/12/2010 9:14 AM, Rainer Frey wrote:
> > I understand that, but would it be possible/good/not causing problems to
> > change this to do CATALINA_BASE="$CATALINA_HOME first, so a setenv.sh can
> > rely on CATALINA_BASE being set?
>
> I think I understand the source of the confusion, here:
>
> 1. you want CATALINA_BASE to be set before CATALINA_HOME/bin/setenv.sh
> is invoked
yes.
> 2. CATALINA_BASE must be set to something other than CATALINA_BASE
> in order for CATALINA_BASE/bin/setenv.sh to be invoked /at all/
Detecting the right setenv.sh works fine, so I don't care about that.
> 3. case here is that CATALINA_HOME/bin/setenv.sh is being used,
> but you want to use CATALINA_BASE/[something] in your generic scripts
Exactly.
> if [ -n "${CATALINA_BASE}" ] ; then
> THE_BASE_DIR="${CATALINA_BASE}"
> else
> THE_BASE_DIR="${CATALINA_HOME}"
> fi
[...]
> CONF_DIR="${THE_BASE_DIR}/conf"
Thanks for the hint, I'm doing exactly that now.
> I'm not sure a patch is necessary, since the script has all the
> information it needs. Perhaps your script will have to be a bit more
> verbose (for instance, by explicitly testing for CATALINA_BASE), but it
> is certainly not prohibited from doing it's own work.
That's absolutely right. A patch certainly is not necessary. My thought behind
the question was just: would it be better to solve this once for everybody by
changing catalina.sh, instead of let everybody handle that in their own
script?
> if a user is going to use CATALINA_BASE, it
> must be set before any scripts are called, otherwise CATALINA_BASE
> doesn't get used at all (and CATALINA_HOME is the appropriate location
> of whatever configuration files you want to use).
>
> There will be cases where CATALINA_BASE is not set at all, and therefore
> essentially defaults to CATALINA_HOME.
Well, actually, from a few lines down in catalina.sh, CATALINA_BASE *is*
always set (to the value of CATALINA_HOME if not set to anything else). The
rest of the script *does* use CATALINA_BASE unconditionally, and it is used to
set the catalina.base system property which *is* always used by Tomcat
internally.
> It's probably a good thing for setenv.sh to be able to determine whether
> CATALINA_BASE is explicitly set
I did not think I'd ever need this, that's why I asked for other opinions. In
that case my proposed change is undesirable.
>
> Does your setenv.sh script expect to use a default file
> (CATALINA_HOME/conf/whatever.jmx) and allow it to be overridden in
> CATALINA_BASE/conf/whatever.jmx?
No, though it might be a good idea after all. My original plan was to use one
separate file per instance, no matter whether that instance is standalone or
part of a multi-instance setup.
> If so, then your script will have to
> test both locations, anyway, because you'll have to check to see if the
> (optional) override file exists in CATALINA_BASE and then check for it
> again under CATALINA_HOME.
>
> Having a blank CATALINA_BASE seems to be helpful in this situation.
Well, then there *is* reason to leave it as is. That is a helpful answer to my
question.
> Is there a situation that you think doesn't work given the current
> script behavior?
No, and I didn't want to imply that. But in general, one can change something
that already works to make it work a little bit better :-)
Thanks for your time.
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: setenv.sh and CATALINA_BASE
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rainer,
On 7/12/2010 9:14 AM, Rainer Frey wrote:
> I understand that, but would it be possible/good/not causing problems to
> change this to do CATALINA_BASE="$CATALINA_HOME first, so a setenv.sh can rely
> on CATALINA_BASE being set?
I think I understand the source of the confusion, here:
1. you want CATALINA_BASE to be set before CATALINA_HOME/bin/setenv.sh
is invoked
2. CATALINA_BASE must be set to something other than CATALINA_BASE
in order for CATALINA_BASE/bin/setenv.sh to be invoked /at all/
3. case here is that CATALINA_HOME/bin/setenv.sh is being used,
but you want to use CATALINA_BASE/[something] in your generic scripts
Okay, let's start from #2: if a user is going to use CATALINA_BASE, it
must be set before any scripts are called, otherwise CATALINA_BASE
doesn't get used at all (and CATALINA_HOME is the appropriate location
of whatever configuration files you want to use).
There will be cases where CATALINA_BASE is not set at all, and therefore
essentially defaults to CATALINA_HOME. It is in this case that blindly
using CATALINA_BASE in your CATALINA_HOME/bin/setenv.sh script is
inappropriate.
Okay, then don't use it blindly.
How about something like this in your setenv.sh:
if [ -n "${CATALINA_BASE}" ] ; then
THE_BASE_DIR="${CATALINA_BASE}"
else
THE_BASE_DIR="${CATALINA_HOME}"
fi
source "${THE_BASE_DIR}/some_setup_script.sh"
...
> I want to know the path to the conf directory in setenv.sh, and I prefer to do
> that in a manner that does not depend on whether this setenv.sh is used
> in a standard installation with CATALINA_BASE=$CATALINA_HOME or in a multi-
> instance setup with
> distinct CATALINA_BASE and CATALINA_HOME.
CONF_DIR="${THE_BASE_DIR}/conf"
> So my question essentially is: would you be interested in a patch that changes
> catalina.sh, or is there a good reason to leave it as is, and let everybody
> sort this out themselves in their setenv.sh?
It's probably a good thing for setenv.sh to be able to determine whether
CATALINA_BASE is explicitly set, though I suppose if CATALINA_BASE ==
CATALINA_HOME, then there's no distinct CATALINA_BASE.
I'm not sure a patch is necessary, since the script has all the
information it needs. Perhaps your script will have to be a bit more
verbose (for instance, by explicitly testing for CATALINA_BASE), but it
is certainly not prohibited from doing it's own work.
Does your setenv.sh script expect to use a default file
(CATALINA_HOME/conf/whatever.jmx) and allow it to be overridden in
CATALINA_BASE/conf/whatever.jmx? If so, then your script will have to
test both locations, anyway, because you'll have to check to see if the
(optional) override file exists in CATALINA_BASE and then check for it
again under CATALINA_HOME.
Having a blank CATALINA_BASE seems to be helpful in this situation.
Is there a situation that you think doesn't work given the current
script behavior?
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkw/UsYACgkQ9CaO5/Lv0PABlQCfS2x+KmEIpSlSstbKLLILgEjO
ilgAn12X2xi5YhEj8EHwQKWI+uh9TOFg
=0INM
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: setenv.sh and CATALINA_BASE
Posted by Rainer Frey <ra...@inxmail.de>.
On Monday 12 July 2010 14:44:19 Konstantin Kolinko wrote:
> 2010/7/12 Rainer Frey <ra...@inxmail.de>:
> > Hi,
> >
> > in the default case (just one instance, supplied start scripts),
> > CATALINA_BASE is set to CATALINA_HOME. But this assignment,
> >
> > if [ -z "$CATALINA_BASE" ] ; then
> > CATALINA_BASE="$CATALINA_HOME"
> > fi
> >
> > is done *after* reading setenv.sh. Is this for a specific reason, or just
> > accidently?
>
> I think that in the following lines of
> http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/bin/catalina.sh?view=mark
> up
>
> 120 if [ -r "$CATALINA_BASE"/bin/setenv.sh ]; then
> 121 . "$CATALINA_BASE"/bin/setenv.sh
> 122 elif [ -r "$CATALINA_HOME"/bin/setenv.sh ]; then
> 123 . "$CATALINA_HOME"/bin/setenv.sh
> 124 fi
>
> the line 120 should be something like
> if [ -n "$CATALINA_BASE" ] && [ -r "$CATALINA_BASE"/bin/setenv.sh ]; then
>
> (that is already fixed in trunk in a different way).
>
>
> In any case, if CATALINA_BASE is not set,
> $CATALINA_BASE/bin/setenv.sh cannot be read (chicken vs. egg), and in
> that case $CATALINA_HOME/bin/setenv.sh is read.
>
> That is nearly the same result as if there was assignment
> CATALINA_BASE="$CATALINA_HOME" before.
I understand that, but would it be possible/good/not causing problems to
change this to do CATALINA_BASE="$CATALINA_HOME first, so a setenv.sh can rely
on CATALINA_BASE being set?
> So, what is your problem?
> You must set CATALINA_BASE before calling the standard scripts, if you
> need this feature of distinct CATALINA_HOME vs. CATALINA_BASE. This
> feature is not enabled by default.
I want to know the path to the conf directory in setenv.sh, and I prefer to do
that in a manner that does not depend on whether this setenv.sh is used
in a standard installation with CATALINA_BASE=$CATALINA_HOME or in a multi-
instance setup with
distinct CATALINA_BASE and CATALINA_HOME.
If catalina.sh would do CATALINA_BASE=$CATALINA_HOME before sourcing
setenv.sh, I could always use $CATALINA_BASE/conf in setenv.sh, and would not
need to take care of this distinction again.
So my question essentially is: would you be interested in a patch that changes
catalina.sh, or is there a good reason to leave it as is, and let everybody
sort this out themselves in their setenv.sh?
> Best regards,
> Konstantin Kolinko
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: setenv.sh and CATALINA_BASE
Posted by Konstantin Kolinko <kn...@gmail.com>.
2010/7/12 Rainer Frey <ra...@inxmail.de>:
> Hi,
>
> in the default case (just one instance, supplied start scripts), CATALINA_BASE
> is set to CATALINA_HOME. But this assignment,
>
> if [ -z "$CATALINA_BASE" ] ; then
> CATALINA_BASE="$CATALINA_HOME"
> fi
>
> is done *after* reading setenv.sh. Is this for a specific reason, or just
> accidently?
>
I think that in the following lines of
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/bin/catalina.sh?view=markup
120 if [ -r "$CATALINA_BASE"/bin/setenv.sh ]; then
121 . "$CATALINA_BASE"/bin/setenv.sh
122 elif [ -r "$CATALINA_HOME"/bin/setenv.sh ]; then
123 . "$CATALINA_HOME"/bin/setenv.sh
124 fi
the line 120 should be something like
if [ -n "$CATALINA_BASE" ] && [ -r "$CATALINA_BASE"/bin/setenv.sh ]; then
(that is already fixed in trunk in a different way).
In any case, if CATALINA_BASE is not set,
$CATALINA_BASE/bin/setenv.sh cannot be read (chicken vs. egg), and in
that case $CATALINA_HOME/bin/setenv.sh is read.
That is nearly the same result as if there was assignment
CATALINA_BASE="$CATALINA_HOME" before.
So, what is your problem?
You must set CATALINA_BASE before calling the standard scripts, if you
need this feature of distinct CATALINA_HOME vs. CATALINA_BASE. This
feature is not enabled by default.
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: setenv.sh and CATALINA_BASE
Posted by André Warnier <aw...@ice-sa.com>.
Rainer Frey wrote:
> On Monday 12 July 2010 12:17:40 André Warnier wrote:
>> Rainer Frey wrote:
>>> On Monday 12 July 2010 10:56:19 André Warnier wrote:
>>>> Rainer Frey wrote:
>>>>> Hi,
>>>>>
>>>>> in the default case (just one instance, supplied start scripts),
>>>>> CATALINA_BASE is set to CATALINA_HOME. But this assignment,
>>> in catalina.sh
>>>
>>>>> if [ -z "$CATALINA_BASE" ] ; then
>>>>>
>>>>> CATALINA_BASE="$CATALINA_HOME"
>>>>>
>>>>> fi
>>>>>
>>>>> is done *after* reading setenv.sh. Is this for a specific reason, or
>>>>> just accidently?
>>> [reason: using CATALINA_BASE in setenv.sh]
>>>
>> So the question was in order to make sure that we were talking about one of
>> the "official" Tomcat scripts, and trying to figure out when it is
>> invoked.
>>
>> This is still not so certain in your case : how do you start Tomcat, and do
>> you know exactly which non-Tomcat and yes-Tomcat scripts are being called,
>
> I thought that tar.gz-Download was clear enough. Yes this is the official
> download from tomcat.apache.org. Nothing else is involved.
>
>> in what order ? (under Linux, probably start with /etc/init.d/tomcatxx,
>> and see what it does).
>
> As I didn't mention anything apart the <quote>supplied scripts</quote>, there
> is no non-Tomcat script. (A reason that I didn't mention Linux in the first
> mail: people start to assume unmentioned things like init scripts or
> distribution packages ... ;) )
>
>> All this to say that, depending on your Tomcat version and origin,
>> setenv.sh /may/ not be the best place to define CATALINA_BASE.
>
> No! I want to *USE* CATALINA_BASE in my setenv.sh, not define it. I'll try to
> explain again:
> catalina.sh
> * tests if CATALINA_BASE/bin/setenv.sh exists and sources it
> * otherwise tests if CATALINA_HOME/bin/setenv.sh exists and sources it
> * then tests if CATALINA_BASE is empty and, if so, sets
> CATALINA_BASE=$CATALINA_HOME
>
> I want to know the config directory of the Tomcat instance in my setenv.sh.
> The way things are I need to check whether CATALINA_BASE is set, and if not,
> use CATALINA_HOME as base directory.
>
> If catalina.sh would first set CATALINA_BASE to CATALINA_HOME if not set to
> anything else, I could always sue CATALINA_BASE in setenv.sh.
>
> So my question is: are things done the way theyare for a reason, or is this an
> oversight that can be fixed? (in which case I could make a patch and open an
> issue to change that)
>
>> I have not
>> verified, but if catalina.sh looks for setenv.sh in $CATALINA_HOME/bin,
>> then obviously it isn't, if your intention is to run several instances of
>> Tomcat sharing the same bin directory.
>
> No idea how you could imply that from my question. My intention is to have a
> common way to refer to the config directory in setenv.sh in single- and
> multiple-instance (with separate bin-directories) setups.
Usually, people get concerned about CATALINA_BASE when they want to run several instances
of Tomcat. And the whole point of running several instances of Tomcat, is to /share/
CATALINA_HOME/bin between these instances. (Otrherwise, one might as well install Tomcat
several times in separate CATALINA_HOME dirs).
That's maybe why I am a bit confused now..
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: setenv.sh and CATALINA_BASE
Posted by Rainer Frey <ra...@inxmail.de>.
On Monday 12 July 2010 12:17:40 André Warnier wrote:
> Rainer Frey wrote:
> > On Monday 12 July 2010 10:56:19 André Warnier wrote:
> >> Rainer Frey wrote:
> >>> Hi,
> >>>
> >>> in the default case (just one instance, supplied start scripts),
> >>> CATALINA_BASE is set to CATALINA_HOME. But this assignment,
> >
> > in catalina.sh
> >
> >>> if [ -z "$CATALINA_BASE" ] ; then
> >>>
> >>> CATALINA_BASE="$CATALINA_HOME"
> >>>
> >>> fi
> >>>
> >>> is done *after* reading setenv.sh. Is this for a specific reason, or
> >>> just accidently?
> >
> > [reason: using CATALINA_BASE in setenv.sh]
> >
> So the question was in order to make sure that we were talking about one of
> the "official" Tomcat scripts, and trying to figure out when it is
> invoked.
>
> This is still not so certain in your case : how do you start Tomcat, and do
> you know exactly which non-Tomcat and yes-Tomcat scripts are being called,
I thought that tar.gz-Download was clear enough. Yes this is the official
download from tomcat.apache.org. Nothing else is involved.
> in what order ? (under Linux, probably start with /etc/init.d/tomcatxx,
> and see what it does).
As I didn't mention anything apart the <quote>supplied scripts</quote>, there
is no non-Tomcat script. (A reason that I didn't mention Linux in the first
mail: people start to assume unmentioned things like init scripts or
distribution packages ... ;) )
> All this to say that, depending on your Tomcat version and origin,
> setenv.sh /may/ not be the best place to define CATALINA_BASE.
No! I want to *USE* CATALINA_BASE in my setenv.sh, not define it. I'll try to
explain again:
catalina.sh
* tests if CATALINA_BASE/bin/setenv.sh exists and sources it
* otherwise tests if CATALINA_HOME/bin/setenv.sh exists and sources it
* then tests if CATALINA_BASE is empty and, if so, sets
CATALINA_BASE=$CATALINA_HOME
I want to know the config directory of the Tomcat instance in my setenv.sh.
The way things are I need to check whether CATALINA_BASE is set, and if not,
use CATALINA_HOME as base directory.
If catalina.sh would first set CATALINA_BASE to CATALINA_HOME if not set to
anything else, I could always sue CATALINA_BASE in setenv.sh.
So my question is: are things done the way theyare for a reason, or is this an
oversight that can be fixed? (in which case I could make a patch and open an
issue to change that)
> I have not
> verified, but if catalina.sh looks for setenv.sh in $CATALINA_HOME/bin,
> then obviously it isn't, if your intention is to run several instances of
> Tomcat sharing the same bin directory.
No idea how you could imply that from my question. My intention is to have a
common way to refer to the config directory in setenv.sh in single- and
multiple-instance (with separate bin-directories) setups.
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: setenv.sh and CATALINA_BASE
Posted by André Warnier <aw...@ice-sa.com>.
Rainer Frey wrote:
> On Monday 12 July 2010 10:56:19 André Warnier wrote:
>
>> Rainer Frey wrote:
>>> Hi,
>>>
>>> in the default case (just one instance, supplied start scripts),
>>> CATALINA_BASE is set to CATALINA_HOME. But this assignment,
>
> in catalina.sh
>
>>> if [ -z "$CATALINA_BASE" ] ; then
>>>
>>> CATALINA_BASE="$CATALINA_HOME"
>>>
>>> fi
>>>
>>> is done *after* reading setenv.sh. Is this for a specific reason, or just
>>> accidently?
>
> [reason: using CATALINA_BASE in setenv.sh]
>
>> To make clear what you mean and what you are asking, can you indicate
>> exactly what version of Tomcat you are talking about, on which platform,
>> and where you got it from ?
>
> Tomcat 6.0.28 and 7.0.0, tar.gz downloads on Linux (I assumed at least the
> platform was obvious when talking about .sh).
No. First, only for Linux, there are the "official" Tomcat downloads from the Tomcat
website, but also umpteen pre-packaged versions for all Linux variations and versions.
Then there are packaged versions for Solaris, HPUX, AIX and whatnot.
All these pre-packaged versions have a tendency to place Tomcat-related files in various
directories (such as /var/lib/tomcatxx, /usr/share/tomcatxx, /etc/tomcatxx,
/opt/hpws/tomcatxx, and so on, with symlinks all over the place to reconnect the bits and
pieces). They also usually start/stop tomcat via platform-specific scripts in (variously)
/etc/init.d, /etc/rc.d/init.d, /sbin/init.d, and so on.
So the question was in order to make sure that we were talking about one of the "official"
Tomcat scripts, and trying to figure out when it is invoked.
This is still not so certain in your case : how do you start Tomcat, and do you know
exactly which non-Tomcat and yes-Tomcat scripts are being called, in what order ?
(under Linux, probably start with /etc/init.d/tomcatxx, and see what it does).
>
> I assume this is the same situation in all Tomcat 6 and trunk versions.
>
>> Also indicate in which script you find the
>> assignment above, please.
>
> Arggh. I was sure that I have typed catalina.sh somewhere! Must have deleted
> it when reformulating the mail. Thanks for the quick reply!
>
All this to say that, depending on your Tomcat version and origin, setenv.sh /may/ not be
the best place to define CATALINA_BASE. I have not verified, but if catalina.sh looks for
setenv.sh in $CATALINA_HOME/bin, then obviously it isn't, if your intention is to run
several instances of Tomcat sharing the same bin directory.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: setenv.sh and CATALINA_BASE
Posted by Rainer Frey <ra...@inxmail.de>.
On Monday 12 July 2010 10:56:19 André Warnier wrote:
> Rainer Frey wrote:
> > Hi,
> >
> > in the default case (just one instance, supplied start scripts),
> > CATALINA_BASE is set to CATALINA_HOME. But this assignment,
in catalina.sh
> > if [ -z "$CATALINA_BASE" ] ; then
> >
> > CATALINA_BASE="$CATALINA_HOME"
> >
> > fi
> >
> > is done *after* reading setenv.sh. Is this for a specific reason, or just
> > accidently?
[reason: using CATALINA_BASE in setenv.sh]
> To make clear what you mean and what you are asking, can you indicate
> exactly what version of Tomcat you are talking about, on which platform,
> and where you got it from ?
Tomcat 6.0.28 and 7.0.0, tar.gz downloads on Linux (I assumed at least the
platform was obvious when talking about .sh).
I assume this is the same situation in all Tomcat 6 and trunk versions.
> Also indicate in which script you find the
> assignment above, please.
Arggh. I was sure that I have typed catalina.sh somewhere! Must have deleted
it when reformulating the mail. Thanks for the quick reply!
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: setenv.sh and CATALINA_BASE
Posted by André Warnier <aw...@ice-sa.com>.
Rainer Frey wrote:
> Hi,
>
> in the default case (just one instance, supplied start scripts), CATALINA_BASE
> is set to CATALINA_HOME. But this assignment,
>
> if [ -z "$CATALINA_BASE" ] ; then
> CATALINA_BASE="$CATALINA_HOME"
> fi
>
> is done *after* reading setenv.sh. Is this for a specific reason, or just
> accidently?
>
> The reason why I ask is: I want to put some custom config files (specifically:
> jmxremote access and password files) in the conf directory, and setup system
> properties with the path to these files in setenv.sh., but I can't use
> $CATALINA_BASE/conf unconditinally because it is not set at that point by the
> default scripts.
>
> (I don't want to use $CATALINA_HOME/conf uncontitionally either, as I'll use
> this setenv.sh also in a multi-instance setup).
>
To make clear what you mean and what you are asking, can you indicate exactly what version
of Tomcat you are talking about, on which platform, and where you got it from ?
Also indicate in which script you find the assignment above, please.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org