Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of cschneiderpublic@gmail.com
 designates 74.125.82.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <51F7D27D.4080909@gmail.com>
References: 
 <CAJv_xg-EWrObJ_P+h8RZ4ANrOZN3ZLwUt-9iecPZpHKwFNOH=g@mail.gmail.com>
	<51F7D27D.4080909@gmail.com>
Date: Thu, 1 Aug 2013 17:55:49 +0200
Message-ID: 
 <CAJv_xg8ZXAbhaHvsG-NimP3O2VCrB+w66_cN0GWUNeMFKUsp9A@mail.gmail.com>
Subject: Re: Using the bin/daemon.sh script on ubuntu.
From: Christian Schneider <cschneiderpublic@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=001a11c278b638d5ad04e2e4e027

--001a11c278b638d5ad04e2e4e027
Content-Type: text/plain; charset=ISO-8859-1

Thanks for the great responses.

@Ognjen: Yes, currently we also use the setenv.sh (because it will not be
touched by an update).
The *ln -s* Tipp is not bad.
But the problem is, it stores the files in the folder (/opt/tomcat/logs).

On our (AWS) installation we have limited space on /opt, therefore we
attached an EBS volume  to /var/, - otherwise we would get problems with
the log files. Now it can grow above some GB.

But because the log dirs are defined in the logging.properties (what get
shipped and overridden by updates) we put this "hack" into our setenv.sh:

sed -i 's/${catalina.base}\/logs/\/var\/log\/tomcat\//g'
\/opt\/tomcat\/conf\/logging.properties

This will replace the sting *${catalina.base}\/logs* with */var\/log\/tomcat
* everytime setenv.sh is executed.

Now we will never forget to touch the logging.properties after an update.
But i still think it is not that elegant...

Best Regards,
Christian.


2013/7/30 Ognjen Blagojevic <ognjen.d.blagojevic@gmail.com>

> Christian,
>
>
> On 30.7.2013 11:58, Christian Schneider wrote:
>
>> But what about:
>> * set env. variables (maybe: catalina.sh?, /etc/profiles?)
>>
>
> /etc/profiles is executed when you enter bash shell, so if Tomcat starts
> at boot time, it won't be able to access environment variables defined in
> /etc/profile.
>
> I set JAVA_HOME, CATALINA_BASE and CATALINA_HOME environment variables in
> /etc/init.d/tomcat (which is a copy of daemon.sh), but I guess there may be
> a better place to do that.
>
> This link [1] recommends to put environment variables in
> /etc/default/tomcat, and then to source them from /etc/init.d/tomcat.
>
>
>
>  * adjust the heap size
>>
>
> Create file $CATALINA_BASE/bin/setenv.sh:
>
> ----
> export CATALINA_OPTS='-Xms...m -Xmx...m'
> ----
>
>
>
>  * logging to the right directory (like: /var/log/tomcat/...)
>>
>
> Maybe something like:
>
> ln -s /var/log/tomcat $CATALINA_BASE/logs
>
>
>
>  * specifying the User: "tomcat"
>>
>
> User 'tomcat' is already specified in daemon.sh, though you may override
> that with $TOMCAT_USER environment variable.
>
> -Ognjen
>
> [1] http://unix.stackexchange.com/**questions/44370/how-to-make-**
> unix-service-see-environment-**variables<http://unix.stackexchange.com/questions/44370/how-to-make-unix-service-see-environment-variables>
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.**apache.org<users-unsubscribe@tomcat.apache.org>
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

--001a11c278b638d5ad04e2e4e027--