Your message dated Thu, 21 Jul 2016 13:33:19 +0200
with message-id <f1f83100-123c-e190-1d1b-ebe56af5f...@apache.org>
and subject line 
has caused the Debian Bug report #591390,
regarding tomcat6: A stopped tomcat is implicitly restarted on upgrade
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.)


-- 
591390: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tomcat6
Version: 6.0.28-1
Severity: minor

When I do:

    sudo service tomcat6 stop
    sudo aptitude upgrade

tomcat6 will be started again as part of the upgrade:

    Setting up tomcat6 (6.0.28-1) ...
    Installing new version of config file /etc/tomcat6/web.xml ...
    Starting Tomcat servlet engine: tomcat6.

Note however that tomcat6 was still in my rc.d:
    
    $ ls -l /etc/rc?.d/*tomcat*
    lrwxrwxrwx 1 root root 17 Aug  2 18:03 /etc/rc0.d/K02tomcat6 -> 
../init.d/tomcat6
    lrwxrwxrwx 1 root root 17 Aug  2 18:03 /etc/rc1.d/K02tomcat6 -> 
../init.d/tomcat6
    lrwxrwxrwx 1 root root 17 Aug  2 18:03 /etc/rc2.d/S01tomcat6 -> 
../init.d/tomcat6
    lrwxrwxrwx 1 root root 17 Aug  2 18:03 /etc/rc3.d/S01tomcat6 -> 
../init.d/tomcat6
    lrwxrwxrwx 1 root root 17 Aug  2 18:03 /etc/rc4.d/S01tomcat6 -> 
../init.d/tomcat6
    lrwxrwxrwx 1 root root 17 Aug  2 18:03 /etc/rc5.d/S01tomcat6 -> 
../init.d/tomcat6
    lrwxrwxrwx 1 root root 17 Aug  2 18:03 /etc/rc6.d/K02tomcat6 -> 
../init.d/tomcat6

I haven't tested this after doing:

    sudo update-rc.d -f tomcat6 remove

Perhaps this is a non-issue. I haven't found anything in the Debian
policy manual that contradicts it (but I also haven't looked very
much).

But it's uncomfortable to have a manually stopped tomcat be started
again on upgrade.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (700, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.35-rc5-Avar-Akbar+ (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages tomcat6 depends on:
ii  adduser                       3.112      add and remove users and groups
ii  tomcat6-common                6.0.28-1   Servlet and JSP engine -- common f

Versions of packages tomcat6 recommends:
ii  authbind                      1.2.0      Allows non-root programs to bind()

Versions of packages tomcat6 suggests:
ii  tomcat6-admin                 6.0.28-1   Servlet and JSP engine -- admin we
ii  tomcat6-docs                  6.0.28-1   Servlet and JSP engine -- document
ii  tomcat6-examples              6.0.28-1   Servlet and JSP engine -- example 
pn  tomcat6-user                  <none>     (no description available)

-- Configuration Files:
/etc/tomcat6/server.xml changed [not included]
/etc/tomcat6/tomcat-users.xml [Errno 13] Permission denied: 
u'/etc/tomcat6/tomcat-users.xml'

-- no debconf information



--- End Message ---
--- Begin Message ---
Closing, this is a configuration question and not a packaging issue. I
guess SystemD in Jessie helped a bit here since it allows one to disable
a service, then the restart on a package upgrade has no effect.

--- 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.

Reply via email to