Okay I got this working!

The patch that chantra gave did not help here.  Neither did the original
suggestion in the bug description of commenting out one of the
WRAPPER_OPTIONS= lines.

I think this fix will probably work for the following bugs, which are
likely caused by the same error:

65743
70177

What I found was that when the /etc/init.d/mldonkey-server script runs
and tries to start mlnet, it executes an install command with the
invalid -f option.  It seems that the author intended to create a blank
$PIDFILE (/var/run/mlnet.pid) with explicit user, group, and
permissions.  But the author botched that.  For one, the install command
does not take a -f option.  Instead it should have a source and
destination file.  So for another, $PIDFILE I would assume is the
intended destination file but no source file is given.

Looking further, I learned that the following line calls start-stop-
daemon to actually start or kill the mlnet server process.  Since start-
stop-daemon is passed the --pidfile $PIDFILE argument, it will create
the file if it does not exist and populate it with the process id for
the mlnet process.  If the /var/log/mlnet.pid file already exists, then
it will error out and indicate that mldonkey-server (mlnet) is already
running.

SO...  The answer is to simply comment out the install command line, and
it starts to work fine.

This error causes installing (or uninstalling) the mldonkey-server
package with APT or Synaptic (or whatever) to fail as well, because the
script is called to stop and/or start the mlnet daemon as part of the
(un|re)installation.

I don't know how to create patch files, even though it's probably easy.
So instead I will just attach my modified /etc/init.d/mldonkey-server
script.  You can back up or rename your existing one and try mine out in
it's place to see if it fixes you as well.

PEACE!

Tim LePes


** Attachment added: "corrected /etc/init.d/mldonkey-server script"
   http://librarian.launchpad.net/5107933/mldonkey-server

-- 
Startup file doesn't work
https://launchpad.net/bugs/35914

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to