tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <ma...@apache.org>
Subject Re: catalina_out env var
Date Fri, 01 Nov 2019 17:58:45 GMT
On November 1, 2019 3:25:36 PM UTC, Chris Cheshire <yahoonomas@gmail.com> wrote:
>(Tomcat 9, Debian & Centos Unix)
>
>I use systemd to start tomcat with base and home separated using
>catalina.sh. For the service script, values for JAVA_HOME,
>CATALINA_HOME, CATALINA_BASE and CATALINA_OUT are defined there.
>
>Inside catalina.sh it says this about CATALINA_OUT
>
>#   CATALINA_OUT    (Optional) Full path to a file where stdout and
>stderr
>#                   will be redirected.
>#                   Default is $CATALINA_BASE/logs/catalina.out
>
>If this isn't defined, catalina.sh sets a default. It seems that
>everything that goes in here also goes in catalina.date.log
>(controlled by the tomcat's logging.properties), so why does it exist?
>Can I force a redirection to /dev/null instead so I don't have
>duplicated logs?
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>For additional commands, e-mail: users-help@tomcat.apache.org

You can control this in logging.properties  Just disable the console logger.

You don't want redirect to /dev/null as then you will be unable to take thread dumps or anything
else that writes to stdout.

It is setup this way for users running Tomcat directly from the console.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message