cDonkey FAQ English, last updated 02-07-2003
http://cdonkey.suche.org

--- General ----------------------------------------------------------------

* Always use the current release of this software, cdonkey is under constant
  development; your problem might have already been solved.
* If, after reading this faq, you still have problems feel free to discuss 
  them in the forum at http://suche.org/phorum/
  Try to describe your problem as detailed as possible to help other people
  to reproduce and to debug the error you encounter.
* Keep in mind that this software is still development, it might crash, do
  weird stuff - just don't expect it to be perfect by now
* This faq is maintained by Joe Malik, for questions or comments feel free
  to contact him (news.malik@gmx.net) 

--- Compilation issues -----------------------------------------------------

Q: The configure script says it can't find the Berkeley Database.
A: cDonkey requires the Berkeley Database version >= 3.3.
   If you're using debian you need to install libdb4.0-dev as well as
   libdb4.0++-dev (both to be found in testing/unstable). The package
   libdb3 (woody) is not suitable.
   If you installed an appropriate version of the berkeley database and
   still encounter this error try compiling cDonkey without the configure
   script using the instructions found in the file INSTALL

Q: GCC stops with an error and the message like "definition of 'akt' shadows
   previous local/global definition".
A: For debugging purposes the '-Werror' switch has been activated,
   instructing the compiler to treat warnings as errors. Since your not a
   cDonkey developer you don't need this. Remove the flag with the following
   lines after you ran the configure script:

sed s/'-Werror'/' '/ < Makefile > Makefile2 &&
mv Makefile2 Makefile &&
sed s/'-Werror'/' '/ < Makefile.am > Makefile.am2 &&
mv Makefile.am2 Makefile.am &&
sed s/'-Werror'/' '/ < Makefile.am > Makefile.in2 &&
mv Makefile.in2 Makefile.in

Q: Is it possible to import eDonkey2000/mldonkey downloads ?
A: Not yet. Sorry.

Q: I encounter the following (or similiar) error:

   In file included from sGui.h:4,
   from donkey.cpp:15:
   misc.h:5: zlib.h: No such file or directory

A: You need the development package of the zlib library.

Q: I encounter the following (or similiar) error:

   In file included from sCommand.h:120,
   from donkey.cpp:15:
   misc.h:5: db.h: No such file or directory

A: You need the Berekeley Database 3.3 or newer. You can download the
   berkeley database from www.sleepycat.com

Q: How do I do a static compile of cDonkey ?

A: Run the configure script and issue the following commands before 
   running the makefile

sed s/'-rdynamic'/'-rdynamic -all-static'/ < Makefile > Makefile2 &&
mv Makefile2 Makefile &&
sed s/'-rdynamic'/'-rdynmaic -all-static'/ < Makefile.am > Makefile.am2 &&
mv Makefile.am2 Makefile.am &&
sed s/'-rdynamic'/'-rdynamic -all-static'/ < Makefile.am > Makefile.in2 && 
mv Makefile.in2 Makefile.in

   There's also an interesting thread covering that topic on the cdoneky
   page you should read (http://suche.org/phorum/viewtopic.php?t=55)   

--- Using the core and gui -------------------------------------------------

Q: The GUI doesn't connect to the core.
A: By default the core listens for the gui on port 9003. Furthermore you
   need to supply a username and a password. The portnumber, username and
   password can be altered through the configuration file of cdonkey. See next
   question for more information.

Q: How to configure the core ?
A: This is achieved with the file ~/.donkey_options (you have to create this
   file yourself):

   client_name = muster
   control = control   
   incoming = incoming
   my_version = 1661    
   server_port = 9001   
   client_port = 9002   
   gui_port = 9003      
   ctrl_user = mein_name
   ctrl_pass = geheim   
   verbose = 0
   tcp_server_count = 150
   tcp_client_count = 150

   The information entered at 'gui_port', 'ctrl_user' and 'ctrl_pass' need
   to be the same as those you enter in the gui.

Q: The GUI can't find a running donkey process.
A: The GUI ist unable to detect cDonkey. To solve this problem you must 
   replace 'localhost' in the first field of the connect dialog with the 
   name of your computer. This makes the GUI think the core resides on 
   a different computer and thus the gui doesn't insist on a local core.
