Re: [Mldonkey-users] donkey servers

[Goswin Brederlow]

Philip Hofstetter <address@hidden> writes:

> Hi,
> 
> Ralf Schmitt wrote:
> 
> >   Now I let mldonkey run just at night, because i tooks ALL my bandwith
> >   at day and I can't browse anymore. But now cvs 5-10-02 doesn't
> >   connects any edonkey server at all. I type 'c' but mldonkey doesn't
> >   care and with zero servers I can't search anything 8(. It would be
> >   great to have some readable output from the core like "trying to connect
> >   server xyz" or "server xyz refused connection"
> >   to be sure mldonkey is doing something.
> 
> I have this exact behaviour if I accidentally try to launch MLDonkey
> two times. This happens when I kill the core with kill <pid>> and it
> does not shutdown properly but stay hanging. When I do not notice this
> and relaunch the core (actually starting it a second time), I can
> connect to this new core, but it is unable to connect to the donkey
> network.

Never kill donkey with kill <pid>, use one of the frontends and issue
the kill command. Otherwise your core will not save it status and you
loose downloads.
 
> I cannot fully explain this behaviour but a "killall -9 mldonkey"
> (don't do this on a System V Derivate as killall works quite
> differently there ;-) ) and restarting it cures the problem for me
> (and kills the old, hanging core, too).

It should complain about not being able to bind to the proper
ports. Without the ports it of cause can't work.

MfG
        Goswin