From MLDonkey
Jump to: navigation, search

Normal use

Before 2.6.1, MLdonkey stored several configuration files in the current directory.
So starting the core from the same directory every time mattered.
With those versions, it's best to create an empty directory, and to always cd to that directory before starting mlnet.

Now, *.ini are saved in $HOME/.mldonkey (unless $MLDONKEY_DIR is set, see below), so current directory doesn't matter anymore.

  1. Simple, displaying initial output, then silent in shell:
* $ mlnet
  1. Displaying continuous output:
* $ mlnet -stdout true
  1. As a daemon, instantly in the background:
* $ mlnet -daemon
(this setting has been removed in as it did not work)
or * $ mlnet &> /dev/null & or * $ mlnet > /dev/null 2>&1 & or * $ mlnet </dev/null >/dev/null 2>/dev/null &
  1. Logging startup messages to file:
* $ mlnet &> file &
  1. Logging runtime messages to file:
* $ mlnet -log_file file  (or set log_file in configuration file)

NOTE: as for older versions, the executable is called mldonkey, not mlnet.

NOTE 2: Setting the environment variable $MLDONKEY_DIR to the path where MLdonkey should save its settings is a working alternative to using the current directory as described above. This works well since


Use the previous information in combination with screen, allowing you to view output from mlnet, while disconnecting and reconnecting, running mlnet in the background.

On Mac OS X, open Terminal, then choose File, Save As..., with the radio button selected "Execute this command", and "Execute this command in a shell". Put in the following, substituting /volumes/bigmac/mldonkey for the path to mlnet

nohup mlnet & (Runs in background, stdout appended to ./nohup.out) On many modern unixy systems StartingSysVStyle is preferred

See Also


Personal tools