Bug#522035: marked as done (mldonkey-server: No log messages written to either /var/log or syslog)
Your message dated Thu, 23 Apr 2009 10:28:17 +0200
with message-id <49F026A1.1000100@pps.jussieu.fr>
and subject line Re: Bug#522035: mldonkey-server: No log messages written to either /var/log or syslog
has caused the Debian Bug report #522035,
regarding mldonkey-server: No log messages written to either /var/log or syslog
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 owner@bugs.debian.org
immediately.)
--
522035: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522035
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: mldonkey-server: No log messages written to either /var/log or syslog
- From: Dmitry Maksyoma <ledestin@gmail.com>
- Date: Tue, 31 Mar 2009 22:19:20 +1300
- Message-id: <20090331091919.11790.94406.reportbug@strekoza>
Package: mldonkey-server
Version: 2.9.5-2+lenny1
Severity: normal
mlnet doesn't log any messages to /var/log/mldonkey/mlnet.log or syslog.
strekoza:/home/ledestin# ll /proc/10757/fd | grep /var/log
strekoza:/home/ledestin# ll /proc/10757/fd | grep log
strekoza:/home/ledestin# ll /proc/10757/fd/{0,1,2}
lrwx------ 1 mldonkey mldonkey 64 2009-03-31 22:04 /proc/10757/fd/0 -> /dev/null
lrwx------ 1 mldonkey mldonkey 64 2009-03-31 22:04 /proc/10757/fd/1 -> /dev/null
lrwx------ 1 mldonkey mldonkey 64 2009-03-31 22:04 /proc/10757/fd/2 -> /dev/null
-- System Information:
Debian Release: 5.0
APT prefers proposed-updates
APT policy: (500, 'proposed-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Shell: /bin/sh linked to /bin/bash
Versions of packages mldonkey-server depends on:
ii adduser 3.110 add and remove users and groups
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii dpkg 1.14.25 Debian package management system
ii libc6 2.7-18 GNU C Library: Shared libraries
ii libfreetype6 2.3.7-2 FreeType 2 font engine, shared lib
ii libgcc1 1:4.3.2-1.1 GCC support library
ii libgd2-noxpm 2.0.36~rc1~dfsg-3 GD Graphics Library version 2 (wit
ii libjpeg62 6b-14 The Independent JPEG Group's JPEG
ii libpng12-0 1.2.27-2+lenny2 PNG library - runtime
ii libstdc++6 4.3.2-1.1 The GNU Standard C++ Library v3
ii mime-support 3.44-1 MIME files 'mime.types' & 'mailcap
ii ucf 3.0016 Update Configuration File: preserv
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime
mldonkey-server recommends no packages.
Versions of packages mldonkey-server suggests:
pn makejail <none> (no description available)
-- debconf information:
mldonkey-server/max_hard_download_rate: 20
* mldonkey-server/launch_at_startup: true
mldonkey-server/max_alive: 48
mldonkey-server/run_as_user: mldonkey
mldonkey-server/reown_file: false
mldonkey-server/mldonkey_group: mldonkey
mldonkey-server/mldonkey_niceness: 0
mldonkey-server/false_password:
mldonkey-server/fasttrack_problem:
mldonkey-server/mldonkey_dir: /var/lib/mldonkey
mldonkey-server/mldonkey_move: false
mldonkey-server/max_hard_upload_rate: 10
--- End Message ---
--- Begin Message ---
Mehdi Dogguy wrote:
>
> start-stop-daemon --start $WRAPPER_OPTIONS \
> --pidfile $PIDFILE --background --exec $EXEC \
> -- -log_to_syslog true -pid $PIDDIR
>
> Logs can be found then in /var/log/syslog
>
I assume that this bug can be safely closed as it's fixed in 3.0.0-2…
For stable users, they have to modify the init script to use syslog as
shown above.
Cheers,
--
Mehdi Dogguy مهدي الدقي
http://www.pps.jussieu.fr/~dogguy
Tel.: (+33).1.44.27.28.38
--- End Message ---
Reply to: