It took time to investigate what's happening on Ubuntu.
On Ubuntu, we don't have apparent problem with current setup.
We don't have to touch catalina.out simply because it is
not used.
# Cloudstack java stdout is sent to /dev/null.
In tomcat6, java stdout,stderr is redirected to catalina.out
(in /usr/share/tomcat6/bin/catalina.sh)
So, the init script touches catalina.out before invoking
catalina.sh. Additionally, there's logrotate configuration
in tomcat6 package, which will be installed at
/etc/logrotate.d/tomcat6 during postinstall.
IMHO, it is preferable to have our catalina.out, but
there's no need to fix it in haste.
(2013/06/05 15:38), Hiroaki KAWAI wrote:
Hum... interesting. In Ubuntu tomcat6, the catalina.out
is handled in init script.
1. Download tomcat6_6.0.35-6.debian.tar.gz from
http://packages.ubuntu.com/raring/tomcat6
2. untar it and look into the init script
--------------------
:
touch "$CATALINA_PID" "$CATALINA_BASE"/logs/catalina.out
chown $TOMCAT6_USER "$CATALINA_PID" "$CATALINA_BASE"/logs/catalina.out
:
--------------------
I'd like to put a patch in reviewboard soon.
(2013/06/04 14:49), Prasanna Santhanam wrote:
On Tue, Jun 04, 2013 at 11:26:01AM +0900, Hiroaki KAWAI wrote:
HI,
I looked into tomcat6.spec file, the catalina.out
stuff seems to be handled in rpm installation process.
------------------------
%install
:
/bin/touch ${RPM_BUILD_ROOT}%{logdir}/catalina.out
:
%files
:
%attr(0644,tomcat,tomcat) %{logdir}/catalina.out
:
------------------------
So I'd like to suggest to do as such in our cloudstack spec file, too.
Thanks, this is more elegant for RPMs. I'm trying the fix now. But the
hack I put in should work for debian packages too.
