[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#359237: marked as done (mldonkey-server: provides few log lines at daemon startup)

Your message dated Tue, 11 Jul 2006 09:17:20 -0700
with message-id <E1G0KvI-0002fU-4m@spohr.debian.org>
and subject line Bug#359237: fixed in mldonkey 2.7.7-3
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: mldonkey-server
Version: 2.7.1-2
Severity: wishlist



	Hi!

First, thanks for your work for this package. This is a very usefull and
rather difficult package to do..!

Then, I think it would be interesting to provide few line of log at
daemon startup. Very often, when the daemon fails to starts, it is
because an obvious reasion, but it is difficult to find it in the log.

Today, my daemon refused to start.. After removing two (!) pid files
that the startup script complained about, it still refused to start.
After removeing the --daemon option from the init.d script, I got this:
Launching MLnet process
2006/03/27 14:26:25 Starting MLDonkey 2.7.3 ...
2006/03/27 14:26:25 Language FR, locale ISO-8859-1, ulimit for open
files 1024
2006/03/27 14:26:25 MLDonkey is working in .
2006/03/27 14:26:25 ./config_files_space.tmp exists.
This means another MLDonkey process could still be working
in this directory. Please shut it down before starting
a new instance here. If you are sure no other process uses
this directory delete config_files_space.tmp and restart the core.

which solved my issue :)

Maybe an option like /etc/init.d/mldonkey-server start-no-daemon, or
else would be very helpfull in those cases.


Romain


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-powerpc
Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1)

Versions of packages mldonkey-server depends on:
ii  adduser                       3.85       Add and remove users and groups
ii  debconf [debconf-2.0]         1.4.72     Debian configuration management sy
ii  dpkg                          1.13.17    package maintenance system for Deb
ii  libbz2-1.0                    1.0.3-2    high-quality block-sorting file co
ii  libc6                         2.3.6-4    GNU C Library: Shared libraries an
ii  libfreetype6                  2.1.10-1.2 FreeType 2 font engine, shared lib
ii  libgcc1                       1:4.0.3-1  GCC support library
ii  libgd2-noxpm                  2.0.33-3   GD Graphics Library version 2 (wit
ii  libjpeg62                     6b-12      The Independent JPEG Group's JPEG 
ii  libpng12-0                    1.2.8rel-5 PNG library - runtime
ii  libstdc++6                    4.0.3-1    The GNU Standard C++ Library v3
ii  mime-support                  3.36-1     MIME files 'mime.types' & 'mailcap
ii  ucf                           2.007      Update Configuration File: preserv
ii  zlib1g                        1:1.2.3-11 compression library - runtime

mldonkey-server recommends no packages.

--- End Message ---
--- Begin Message --- 
Source: mldonkey
Source-Version: 2.7.7-3

We believe that the bug you reported is fixed in the latest version of
mldonkey, which is due to be installed in the Debian FTP archive:

mldonkey-gui_2.7.7-3_i386.deb
  to pool/main/m/mldonkey/mldonkey-gui_2.7.7-3_i386.deb
mldonkey-server_2.7.7-3_i386.deb
  to pool/main/m/mldonkey/mldonkey-server_2.7.7-3_i386.deb
mldonkey_2.7.7-3.diff.gz
  to pool/main/m/mldonkey/mldonkey_2.7.7-3.diff.gz
mldonkey_2.7.7-3.dsc
  to pool/main/m/mldonkey/mldonkey_2.7.7-3.dsc



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 359237@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Samuel Mimram <smimram@debian.org> (supplier of updated mldonkey package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Fri, 23 Jun 2006 15:18:15 +0000
Source: mldonkey
Binary: mldonkey-gui mldonkey-server
Architecture: source i386
Version: 2.7.7-3
Distribution: unstable
Urgency: low
Maintainer: Debian OCaml Maintainers <debian-ocaml-maint@lists.debian.org>
Changed-By: Samuel Mimram <smimram@debian.org>
Description: 
 mldonkey-gui - Graphical frontend for mldonkey based on GTK
 mldonkey-server - Door to the 'donkey' network
Closes: 359237 375921 377574
Changes: 
 mldonkey (2.7.7-3) unstable; urgency=low
 .
   * Added 03_lock_config_files_space.dpatch in order to handle leftover
     config_files_space.tmp files, closes: #359237.
   * Removed obsolete configure options, closes: #375921. Also removed Soulseek
     and Opennap from the description.
   * Updated french debconf templates translation, closes: #377574.
   * Depend on ocaml-base-nox instead of ocaml-base on non native archs.
Files: 
 55bfb2ac673e30ef08e6a2accdf91bf5 947 net optional mldonkey_2.7.7-3.dsc
 d8688fab131c51cc6f32c8aaf8684b61 114415 net optional mldonkey_2.7.7-3.diff.gz
 9a3670715290fc59f4dc0ce37c3c880e 2867086 net optional mldonkey-server_2.7.7-3_i386.deb
 892e2aa8918fe6460c10b2c15308f68a 3338244 net optional mldonkey-gui_2.7.7-3_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFEs81LIae1O4AJae8RAl66AJwN74MikwPxH2H9cGTS3TfqMdh3HACggL5P
dVWhPGRxpsOS3BPovZJuACw=
=D3jB
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: