----- Forwarded message from  -----

Date: Sun, 23 Apr 2006 07:04:33 -0700
To: Romain Beauxis <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#359237: mldonkey-server: provides few log lines at daemon 
startup
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.11+cvs20060126
Status: RO

Hello,

On Mon, Mar 27, 2006 at 02:32:20PM +0200, Romain Beauxis wrote:
> 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
>

Well, i take into account your remark. I will try to find a solution

Thanks for the report
Kind regard
Sylvain Le Gall


ps: i have almost no internet connection at this time, so don't expect a
fast correction.

----- End forwarded message -----



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to