Your message dated Sat, 9 Dec 2006 20:32:47 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Change the run level of tomcat from 20 to 90
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: mysql-server-4.1
Version: 4.1.11a-4sarge2
Severity: important

On runlevel change, MySQL init.d script starts and stops at level 20, like 
many other servers like tomcat. I think it should use a level less than 20 
(19 for instance), so that the databases are available for Web applications 
when the Web servers starts, and are still there when the same Web
applications must save data before shutting down.

Or perhaps should I report this bug to tomcat4 maintainer, to increase
tomcat start/stop levels (apache2 is using level 91). But I think other
services like snort (level 20 too) could need a database available at
startup...

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-3-686
Locale: LANG=fr_CA, LC_CTYPE=fr_CA (charmap=ISO-8859-1)

Versions of packages mysql-server-4.1 depends on:
ii  adduser          3.63                    Add and remove users and groups
ii  debconf          1.4.30.13               Debian configuration management sy
ii  libc6            2.3.2.ds1-22            GNU C Library: Shared libraries an
ii  libdbi-perl      1.46-6                  Perl5 database interface by Tim Bu
ii  libgcc1          1:3.4.3-13              GCC support library
ii  libmysqlclient14 4.1.11a-4sarge2         mysql database client library
ii  libncurses5      5.4-4                   Shared libraries for terminal hand
ii  libreadline4     4.3-11                  GNU readline and history libraries
ii  libstdc++5       1:3.3.5-13              The GNU Standard C++ Library v3
ii  libwrap0         7.6.dbs-8               Wietse Venema's TCP wrappers libra
ii  mailx            1:8.1.2-0.20040524cvs-4 A simple mail user agent
ii  mysql-client-4.1 4.1.11a-4sarge2         mysql database client binaries
ii  mysql-common-4.1 4.1.11a-4sarge2         mysql database common files (e.g. 
ii  passwd           1:4.0.3-31sarge5        change and administer password and
ii  perl             5.8.4-8sarge3           Larry Wall's Practical Extraction 
ii  psmisc           21.5-1                  Utilities that use the proc filesy
ii  zlib1g           1:1.2.2-4.sarge.2       compression library - runtime

-- debconf information:
  mysql-server-4.1/start_on_boot: true
  mysql-server-4.1/postrm_remove_databases: false
* mysql-server-4.1/mysql_install_db_notes:
  mysql-server-4.1/mysql_update_hints1:
  mysql-server-4.1/nis_warning:


--- End Message ---
--- Begin Message ---
Version: 5.5.20-3

Fixed in experimental. tomcat5.5 is now started at sort order 90, right before 
apache2.

Since the Tomcat startup mechanism (both jsvc and the old one) does not notify 
when Tomcat initialization is complete, it cannot be guaranteed that Tomcat 
will be ready by the time Apache tries to connect to it. This may potentially 
cause problems, and the only good solution seems to be to add this 
functionality to Tomcat and commons-daemon.


--- End Message ---
_______________________________________________
pkg-java-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers

Reply via email to