Aha, but it _is_ true, although I must admit I'm not entirely correct too

This is what happens if you try the daemon the first time:
[blabla@bla blabla]$ amuled
amuled: OnInit - starting timer
Initialising aMule
Checking if there is an instance already running...
Credits: Failed to load creditfile
Credits: Created new RSA keypair
Loading temp files from /home/blabla/.aMule/Temp.
All PartFiles Loaded.
MuleUDPSocket: Created Server UDP-Socket at port 4665
ListenSocket: Ok.
MuleUDPSocket: Created Client UDP-Socket at port 4672
External connections disabled in config file
*** Server UDP socket (TCP+3) at 0.0.0.0:4665
*** TCP socket (TCP) listening on 0.0.0.0:4662
*** Client UDP socket (extended eMule) at 0.0.0.0:4672
Empty dir /home/blabla/.aMule/Incoming/ shared
General: CamuleDaemonApp::OnRun()
ERROR: aMule daemon cannot be used when external connections are disabled. To enable External Connections, use either a normal aMule or set the key"AcceptExternalConnections" to 1 in the file ~/.aMule/amule.conf
MuleUDPSocket: Shutting down Client UDP-Socket
Now, exiting main app...
aMule OnExit: Terminating core.
MuleUDPSocket: Shutting down Server UDP-Socket
aMule shutdown completed.
Ergo: It creates a config directory BUT fails to start because the default setting in the amule.conf file is incorrect....... If one does not edit the configuration file to enable external connections, one can try this very often without success. Also, if one starts the amuled detached, one will never find this error, since the logs aren't flushed. (btw, Kry, will this be fixed before the next release?)