Your message dated Thu, 21 Jul 2016 14:11:06 +0200
with message-id <8dc6557a-8ca8-93e9-15f5-aa6910de6...@apache.org>
and subject line Re: Trigger implentation to restart tomcat after a web
application has been installed/upgraded
has caused the Debian Bug report #570485,
regarding Trigger implentation to restart tomcat after a web application has
been installed/upgraded
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
570485: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tomcat6
Version: 6.0.24-1
Severity: wishlist
Tags: patch
Please consider adding a trigger which can be used by web application packages
to restart tomcat after they install or upgrade their files
-- System Information:
Debian Release: 5.0.4
APT prefers stable
APT policy: (980, 'stable'), (970, 'stable'), (950, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.30 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
diff -wurN tomcat6-6.0.24/debian/tomcat6.postinst tomcat6-6.0.24.triggers/debian/tomcat6.postinst
--- tomcat6-6.0.24/debian/tomcat6.postinst 2010-01-30 07:39:47.000000000 +0100
+++ tomcat6-6.0.24.triggers/debian/tomcat6.postinst 2010-02-18 14:13:33.326494314 +0100
@@ -2,6 +2,16 @@
set -e
case "$1" in
+ triggered)
+ if [ "$2" = "tomcat6-restart" ]; then
+ if [ -x "`which invoke-rc.d 2>/dev/null`" ]; then
+ invoke-rc.d tomcat6 restart || true
+ else
+ /etc/init.d/tomcat6 restart || true
+ fi
+ fi
+ ;;
+
configure)
if ! id tomcat6 > /dev/null 2>&1 ; then
adduser --system --home /usr/share/tomcat6 --no-create-home \
@@ -34,8 +44,10 @@
;;
esac
+if [ "$1" != "triggered" ]; then
if [ ! -d /var/lib/tomcat6/webapps/ROOT ]; then
cp -r /usr/share/tomcat6/webapps/default_root /var/lib/tomcat6/webapps/ROOT
fi
+fi
#DEBHELPER#
diff -wurN tomcat6-6.0.24/debian/tomcat6.triggers tomcat6-6.0.24.triggers/debian/tomcat6.triggers
--- tomcat6-6.0.24/debian/tomcat6.triggers 1970-01-01 01:00:00.000000000 +0100
+++ tomcat6-6.0.24.triggers/debian/tomcat6.triggers 2010-02-18 12:24:15.339046612 +0100
@@ -0,0 +1 @@
+interest tomcat6-restart
--- End Message ---
--- Begin Message ---
Closing, I agree that restarting the container when installing a webapp
is not a good idea. If this is really needed the package can restart
Tomcat in its postinst script. But this shouldn't be enforced by a
trigger applicable to any webapp.
--- End Message ---
__
This is the maintainer address of Debian's Java team
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>.
Please use
debian-j...@lists.debian.org for discussions and questions.
